[realname] Real Name

I'm really excited for this functionality. What is still required for the 8.x version to be implemented before providing a dev release?

With a beta on its project page status needs to be: Needs review.

Once a stable is released status can be set to fixed.

I do not need the stupid banner on project home.

As far as I know that banner is not optional.
The only way I know to get rid of it is to release a stable version.
You can always file a feature request for opting out of the banner.

Unless the people in control of this project allow for this exception, the rules apply to everyone, as they should.

Stop changing the status. It is my decission when the project is stable.

@hass - Totally not trying to be rude when saying this, but the reason these issues / the contrib tracker exists at all is to be able to provide a general health check on D8 contrib; and additionally, to motivate maintainers to push out a stable release once the module is stable (since a lot of people are scared off by beta/rc releases).

If you think the project is stable, might you consider releasing a final version (or at a minimum an rc)? Right now I only see the 8.x-1.0-beta1 release from a few days ago.

I'm not going to switch the status here, because I respect your wishes as a maintainer, but I'd also like to encourage releasing a stable release if you think the module is, in fact, stable (e.g. not going to change underlying API/foundation).

Request the same from you, stop changing the status.

It is your call to declare the D8 port of your module as Stable, it is not your call to provide incorrect information in this project!
Not even when you are the maintainer of that particular module.

In this project the status 'Needs review' reflects the actual status of your module, as determined by you in your project.
See https://www.drupal.org/project/contrib_tracker#statuses for correct usage of the status in this project.

You might want to have look at https://www.drupal.org/node/2578191#comment-12065170, you are not the only one having a problem with understanding how this project works.

Assuming the same rules apply to everyone, I'll keep changing it back to the correct status. Unless the people in charge here tell me to stop. My understanding is that you are not one of them, please correct me when I am wrong about that. Just for the record, being the maintainer of a module doesn't make in charge in this project!

Still only a beta available!

Again this is MY decission and NOT yours! You are not a developer, never shared a patch and only complain. Go away play somewhere else or I write an automated case-close bot.

Won't repeat myself like you do. Awaiting advise from the webmaster here on how to deal with those that sabotage this project!

For others still interest in this module: No Stable release available, only a beta. Although the maintainer is also working on it, he seems to prefer to waste his time here! Suggest to start looking for alternatives!

I never asked for bullshit on any of the project homes I maintain. Go home.

@mmjvb: I hope discouraging people from working on modules/patches isn't your intention. Pick your battles wisely. Your need for regulation does not outweigh the fact that you are potentially preventing a module maintainer from providing the community his work. More often than not, the labor involved is not paid for and it is a free service provided by module maintainers. This means that it is purely from motivation and wanting to contribute. This only discourages someone from offering their free time.

There are countless other problems in issue queues that deserve your attention more than this.

Edit: Looking at his post history, he appears to be harassing other module maintainers as well: https://www.drupal.org/node/2578191#comment-12055875.

I would love to pay if people were working the way they should. The weakness of Drupal makes it ridiculous. Waiting years for something that would be done within 1 month on Wordpress.

@drupalinthailand: This is really not the place to bring up such concerns. There are plenty of other threads where you can vent.

Edit: It looks like drupalinthailand was also harassing other maintainers. Reference: https://www.drupal.org/node/2578191#comment-12046568

@NWOM Thank you for your opinion. Obviously we disagree, following procedure is not considered harassing!
I requested the webmaster to intervene, I'll be glad to add your name to the list.

The insulting tone here is new to me on d.o. Maybe you'd like to leave us?

You both guys, go out of this issue, please. Spend your time on something that makes sense e.g. WRITE PATCHES and fix issues and share the fixes. I will not create a final release only because a non-developer do not understand anything except green and red.

Before complaining more - stop whining - fix core issues like #2629286: Use getDisplayName() for user names consistently? Something that makes realname stable. Before you have not shared any commitable patch in any of my queues - shut up. You are not the maintainer.

Already requested the webmaster to intervene. The next step will be requesting removal of your edit rights here.
Or take away ownership of this module. Maybe even blocking your account here.

Just for the record, I have had no say in the current policy. But that policy applies to all of us. So, comply or leave!

@NWOM Don't know where you got the idea that discouraging people is my intention.
Thinking such a thing says more about you than me.
Request you to refrain from posting these things here, they are considered off-topic.

Thank you for the advice and may I return the favor: Pick your battles wisely.

As pointed out several times both your behaviour is not acceptable and will have consequences when you continue.
No way people should be allowed to violate the rules in order to preserve their contribution. Having said that, I
would advice anyone contemplating to stop because they have to follow rules, to go see a doctor.
Discussing such irrational sentiments should be enough, otherewise they have medicins.

So, back to the issue: Blocking Stable: https://www.drupal.org/node/2629286

@drupalinthailand - Comment #32 has been removed for violating the Drupal.org Terms of Service - Section C.

The content you publish will not contain any material which is defamatory, obscene, indecent, abusive, offensive, harassing, violent, hateful, inflammatory or otherwise objectionable.

However upset you may be with the progress of a module's development, we will not tolerate harassment and personal attacks.

The use of this queue is not a must. There is no force that every module need to be listed and have the proper status.

It is a nice to have feature that provides information to a handful of people and no more and I do NOT like to see this on my projects.

@hestenet: Please lock the case as closed (fixed).

The Drupal Community Working Group has received multiple incident reports about this thread. We would ask all participants to abide by the Drupal Code of Conduct (https://www.drupal.org/dcoc) when engaging with others, in particular the following:

Be respectful.
The Drupal community and its members treat one another with respect. Everyone can make a valuable contribution to Drupal. We may not always agree, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the Drupal community to be respectful when dealing with other contributors as well as with people outside the Drupal project and with users of Drupal.

We expect individuals to first try to resolve conflicts between themselves in a constructive manner, asking for help when needed, in accordance with our established conflict resolution policy and process (https://www.drupal.org/conflict-resolution) to resolve their dispute

The CWG meets weekly and will review this issue at our next regular meeting, but in the meantime, we ask for participants to be considerate, respectful and collaborative when engaging with each other.

I thought it's only me that felt a bit uncomfortable by such overzealous comments as #2607038-74: [backup_migrate] Backup and Migrate
Looks like I was wrong and mmjvb is really jumping the shark left front and center here.

Anyway moving on, @hass is there anything we can do to help you with https://www.drupal.org/node/2629286 ?

It's so great and we are so lucky that people are working on these modules for free. Thank you so much to all.

Awaiting and anticipating the ruling of CWG resetting this issue to reflect the actual status.

Convinced that the ruling will be that the behavior of hass in this matter is in violation of the CoC.
Contrary to others in this community, I will respect the CoC and the decission of CWG no matter the outcome.

Verified that there is no Stable released, set Status to Needs review.

@Alex: Getting the patch - green and RTBC is priority. It takes a lot of time/debugging to learn why the broken tests are not working properly. Only the tests are currently broken...

With 8.x-1.0-rc1 status should be RTBC.

Related issue : https://www.drupal.org/node/2881931

I'm still curious about that follow up on #39.

What happens here is nothing short of ridiculous.

Correct. Do not touch the status again.

I'm not sure what should be the correct status for this issue as per the current state of the project. Here's the link which could help to set the status https://www.drupal.org/project/contrib_tracker#statuses

//Naveen

There is a useless box on the project home that nobody needs and that should NOT be shown there. The status fixed removes the box. The module is stable. There are only reasons not in my hand that block a RTM, see #2881939: Roadmap D8 final. Keep the status as fixed now.

@naveen As mentioned many times with a RC release the Status should be RTBC to reflect that. That is what the documentation says!
The only way allowed in this project is to release a Stable. That is the way to get rid off the box. See no reason why Real name should be an exception to the rule, just because of the nasty attitude of Haps in this issue!

Requested intervention before, in addition of the issue in the Webmaster queue. So far, no response received!
Do I really have to script the correction, as hass appears to have done. Please intervene?

#74 gives a good explanaition why hass wants this fixed. I fail to see why mmjvb insists on policing this queue and going completely dogmatic on hass and other people who actually work on code.

I am closing comments here! If you need to pursue this further bring it to the CWG. This turf war brings nothing good to the community.