Drupal.org is huge website the migration can take some time. The migration from Drupal 6 to Drupal 7 was finally done 2 years ago and it took forever. Moving forward to Drupal 8 is going to take a lot time. I do not see that happening like in 3 to 4 years.
Moving to Drupal 8 is not a higher priority right now for Drupal.org, compare to adding new features ...
Well the "Bad Judgment" module you linked to claims:
This module provides an explicit dependency for modules whose usage requires bad judgement. Joke modules often require "bad judgement".
So I wouldn't take that version number too seriously.
From the core download page you linked to:
Placeholder for the Drupal 9.x release. Not intended for actual ...
For this you need to create a sandbox project and open up an issue in the issue queue of the existing module, posting a link there and urging the maintainer of that project to have a look.
If they wish, they can commit that module as the official 7.x version, or might even add you as a co-maintainer of the module if you are interested. In case they do not ...
There is a lot of infrastructure and dependencies on the drupal.org site, which also exist outside of the core drupal code base. Such as git integration, issue queues, testbot, project hosting. These contrib modules aren't all yet updated to drupal 8 to my knowledge.
For an idea of what is going on with the drupal.org site I recommend reading: https://...
Only full releases get the security shield. Your screenshot only shows a dev version. I don't think the shield was removed from your module, as it wouldn't have had one in the first place since you don't have a full release.
To get the security shield, you'll need to release a full version (one not suffixed with -dev, -alpha or -beta).
** EDIT **
I have ...
I would use hook_requirements() for this, at least in your next version.
It takes severity parameter:
The requirement's result/severity level, one of:
REQUIREMENT_INFO: For info only.
REQUIREMENT_OK: The requirement is satisfied.
REQUIREMENT_WARNING: The requirement failed with a warning.
REQUIREMENT_ERROR: The requirement failed with an ...
Many of the form element properties are listed in the documentation for the FormElement class. The properties described there are:
Then, as ...
PHPStorm patching issues have a long history. I have corresponded with their staff more than once, about a year ago. They told me then, that my issue was taken up to developers, but never actually corrected it. Right now, PHPStorm issues patches incompatible with Drupal.org, and we can do nothing about it.
To create a working legit patch, you need git, and ...
Since the MVVM library is actually a submodule, can I submit the plugin to the Drupal repository if the Drupal-specific parts (just a couple of files) are set up to use Drupal standards?
Yes, as long as your Drupal project conforms to the GIT repo policy - where just one of terms are: "All code should comply to the coding standards." you can commit it (such ...
It's a generic term to encapsulate all the programming interfaces Drupal provides. Any further meaning would have to be inferred from the context of how it was used (FWIW, I've never heard "Drupal API" to refer to the documentation site api.drupal.org).
When specifying a particular component of the Drupal API, you'll often see it labeled with its ...
The PHP version isn't a required key for module .info files, and it's a minimum version of compatibility anyway. So a module could declare itself as requiring PHP5.6, but still work absolutely fine under PHP7. Or it could not declare a minimum version of PHP at all, and still work under PHP7. Or it could declare PHP5.6 as minimum, but not work at ...
No need to deal with tags for the dev branch. Tags are only required for stable releases.
Since you have already added your dev branch you just have to add your files, commit them and push them, like this:
git add path/to/files
git commit -m "Commit message"
git push origin 7.x-1.x
Then you just wait for drupal.org to reroll a new dev version. It takes up ...
Strange, I selected some modules at random and I see dev versions consistently packed 2013-Oct-01. I can't find any one with another date now.
Examples I've tested:
The usage page comes from project_usage_overview(); it's not a View. The only parameters are those provided by Drupal's tablesort API, "sort" and "order".
?sort=asc you've already discovered, and the other parameter changes the sort column (?order=Project would sort by project name).
References to project issues in the form of [#1234] (or [#1234-2] for comments) turn into links automatically
That is from the very bottom of compose tips.
So just replace the colon with a hyphen and your guess would have been perfect.
In order for a Drupal contributed module to be eligible to be tagged as a security monitored project, one or more of the maintainers have to be 'vetted'.
Here is the main Drupal security policy on this. See the "Which Projects are covered" section. There is a link in this to the process of becoming 'vetted'.
Basically, you submit a Drupal.org ...
A pitty that nobody has reviewed your patch so far. I think you should consider posting a question in one of the Drupal.org forums, with some kind of friendly reminder about it. Something like "can anybody help me on this specific issue to get it in status Reviewed & Tested by the Community (RTBC) please?".
By the way: RTBC is not to be considered as a ...
This is simply due to a bug with the statistics module - see Project Download count Decreased - that has affected Drupal.org infrastructure since the middle of April 2015.
Prior to that bug surfacing, I did not observe a single project where the number of downloads were less than the number of installs.
Just now CKeditor Link is reported to have 487 ...
It took me a while to find but this is what I was looking for:
The following node types currently exist on drupal.org:
book book_listing casestudy changenotice forum image organization
packaging_whitelist page project_issue project_core
project_distribution project_drupalorg project_module project_release
Cloning a project as maintainer of that project is done using the following command.
git clone email@example.com:project/a_project.git
The username is always git.
As non-maintainer, the command to clone the project is the following.
git clone https://git.drupalcode.org/project/a_project.git
When I want to clone one of the projects hosted on drupal.org ...
I used the term vetted role because vetted is the term that appears in the user profile, to users that on Drupal.org have the Git administrator role.
In places listing the possible roles Drupal.org can have, Git vetted user is one of them.
Before the ability of opting into security advisory coverage was introduced, that role allowed users to create a full ...
It's a tag that is automatically added when a more recent release for the same branch has been tagged as release that fixes security issues. In the case of the 3.0.1 release, it's the 3.0.2 release.
The Security update tag is manually added from the Security Team, and it cannot be removed once added. (Actually, the release type cannot be anymore changed, ...
Really this is a greater problem, which is "What do I do if I have made a change that could break people's site", because it isn't limited to dependencies, it can be API changes, removing sub modules, functionality changes, markup changes, etc.
In my opinion I think a note that stands out on the project page and also in the release notes is all you really ...
As reported in Installing sandbox projects, sandbox projects don't have download links, since versions are not enabled for them. You need to use git to download the code.
Assuming you mean the PredictionIO module, that doesn't still have code, at the moment; it is reported in its Version control tab.
No code is available for PredictionIO. File an issue ...
Here is a quote from the Drupal.org Roadmap:
... Each year Drupal.org and its sub-sites serve millions of visitors, and thousands of active contributors. It is one of the largest continuously operating Drupal sites in the world. And because of that, it has 15 years of legacy content and features. At this scale, it's impossible to make ...
Drupal 8 has a new versioning system, with the following format:
Minor versions are expected every 6 months (8.1.0 was recently released), and will contain backwards compatible enhancements and new features, but will remain compatible with code written for earlier releases of the same major version.
So Drupal 8.1.x contains new features ...
It is more likely the case that the service that handles the issue updates was down for some period of time. Under normal circumstances pushing a commit to D.O. will update the issue referenced in the commit message no matter what the issue status is set to...