Closed (won't fix)
Project:
Groups.drupal.org
Version:
6.x-1.x-dev
Component:
New Group Proposal
Priority:
Minor
Category:
Task
Assigned:
Reporter:
Created:
12 Jul 2013 at 17:33 UTC
Updated:
9 Aug 2013 at 00:26 UTC
tvn mentioned this group, which hasn't been submitted for moderation yet:
https://groups.drupal.org/%EF%BD%87%EF%BD%84%EF%BD%8F
I think it's worth moderating sooner rather than later, so I'm starting the moderation process here.
Comments
Comment #1
sreynen commented-1 from me. It seems very likely to cause confusion with https://groups.drupal.org/groups-drupal-org
Comment #2
silverwing commented-1 and I'm not even sure where to start...
If we need a How to use Drupal Groups guide, then we could use a dedicated content type for it. Groups doesn't work well for that. Plus, we have a glossary on d.o for basic terms.
The creator of the group has no other content, therefor I'm not sure if they understand the basics of Drupal be in charge of this kind of group.
I can't tell you how much that font is annoying me. Plus, the whole group description as presented is very juvenile, and not in a "We want to make it easy to understand way" either.
Comment #3
tvn commented-1 to the group as well. What silverwing said.
Comment #4
sreynen commented-2 means deletion per the guidelines at https://groups.drupal.org/node/253733 so I deleted the group.
Comment #5
b-d commentedto sreynen = /groups-drupal-org is for FIXing the software of the GDO.
as for mine it's for Guiding the n00bs
Comment #6
b-d commentedTo silverwing;
Since there is NO dedicated content for the Type that's why i made one.
And for the Glossary I would have linked it; IF and When i find it.
I'm not as good as you to have all my content posted in a few days; i got other stuff to do.
The fact i do NOT know the basics is why i created this sandbox and the same reason i have not posted it for moderation.
Which you have prematurely did this on whomsoever's behalf?
and the gdo is not for you; but for the n00bs who are trying to get to know Drupal.
As for the the font; I have my own design aspects to distinguish one line for the other.
Again I haven't finished it yet that is why i haven't posted it for moderation!
Comment #7
b-d commentedTo tvn;
I know you mean well as trying to help; but don't speak for me next time.
Comment #8
sreynen commentedb-d, it's great that you want to help others, and I suggest you slow down a bit and familiarize yourself with the site first. https://groups.drupal.org/about is a good place to start.
Since the group was already rejected, this issue is resolved. We can't un-reject the group even if we reached consensus that it's okay (which seems unlikely). If you want to create a new group in the future, we can moderate that in a new issue, but I strongly suggest consulting others before doing so. The Drupal Code of Conduct has some good advice related to this:
https://drupal.org/dcoc
To clarify the moderation process, groups are subject to moderation on creation. Submitting a group can speed up moderation, but is not necessary.
Comment #9
silverwing commented@b-d
The name G D O (in whatever typography you choose) isn't an appropriate name for a group. It will confuse people. If the group is a Group FAQ, call it that. Or Drupal Group Tips. Something more specific. And, no, that special typography for the name isn't going to happen.
My feeling is that any page (or in this case, group) that's purpose is to help or inform others should use our d.o style guide https://drupal.org/style-guide/content It's a long page, but the Voice part is important. We need to be consistent.
Is a group the best way to present the information you want? I'm not sure. Structure is important, so you'll be using taxonomy to sort things out, and probably create panels to present. Would something be better?
(As an aside, we probably need to audit the help pages to see what we have where.)
Comment #10
b-d commentedthe name can easily be changed, and again as i said this was going to be my sandbox to familiarize myself on the GDO functions. and Restricted to the public as of i'm not yet finished with it. That issue is a minor concern, so i'll move on...
btw thanks for the HELPFULL LINKS ^_^
I was going to make a simpler versions to ease in the new comers like myself to the d.o. Format using the g.d.o format as a sample to integrate them slowly. especially those who don't know php coding etc...
And YES again for the n-th time; it helps me to test out the gdo functions to figure out the Groups interface at the same time present my information. as a Member of a Group i'm Limited to the Functions compared to me being an Admin/Organizer.
I was working on the structure before my group got obliterated. and i have no idea what taxonomy is and hence need to teach my self thru trial and error. there's no hand holding or spoon feeding here. and thru my learning i could find for my self the "better" version.
Also don't know where to ask first in before to creating one. hence the deed.
So i want to make sure that if i create another Group, that it won't be slaughtered beyond retrieval; losing all my hard work.
Not to mention that i wasn't given at least two weeks to Respond before my group got nuked.
Comment #11
sreynen commentedb-d, there's a pretty big gap right now between your perspective and the perspective of others here on what is appropriate content. Until that gap is closed, I suggest making smaller and fewer edits.
I just reverted some changes you made to our moderation guidelines. Some of your changes were good, but they were mixed in with other changes that were problematic for reasons already outlined in this thread. If you have questions about the problems mentioned here, let's talk about it.
Again, it's great that you're eager to jump in and help, but it's also important to discuss significant changes with others before making them, at least until you have a better feel for community standards here. We don't really have a sandbox environment for groups right now. Maybe we should, but we don't. Published groups are immediately visible to everyone on the site, so we can't really leave up an experiment that seems likely to confuse people about the site.
I'm usually around in the #drupal-groups IRC channel if you'd like to discuss further there. I'm setting the status of this back to closed, since we have no action to take here now that the group was rejected, but you're welcome to continue discussing here as well if you have further questions or comments.
Comment #12
ezra-g commentedBased on the thread here and the referenced, edits, I agree with sreynen here.
Comment #13
b-d commentedI admit that the Gap is EXTREMELY HUGE, is the main reason for me to establish my group. a way to shorten the Learning Curve for the n00bs to the d.o standards.
A way to re-orient the mainstream non-coders perspective to d.o perspective.
Me being in my position gives a unique perspective compared to you veterans.
case and point: did you read the Whole Drupal manual before using the progam?
How about i make a group in Group type: Archives then, for my sand box?
I think you meant "Guidelines for Forming New Drupal Groups" cause i didn't touch http://groups.drupal.org/node/253733. Since there is no TALK page like in wiki I'm restricted to a small revision Box for notes. and an empty one is a bit discouraging. also mine was NOT a publish Group; i don't how tvn found it cause I was sure it wasn't it the g.d.o list when i searched it.
Since there's now way to communicate the changes to a specific page/node i found it a bit messy if i edit one small thing and it stacks up a bunch.
How about for new Groups to be posted; before we take any action, a proposal post like in http://drupal.org/forum. We post a proposed Group and when you agree, then we can get to work on our group. It would be nice, if we don't lose ALL our work when rejected. since there's no way for us to find out if an organizer is presently active or not.
As for the IRC; i just learned it a few weeks ago, and i can still remember how oblivious i was thinking how it it was going to be easier for me to understand and use it.
So discussing changes in the IRC is the option then before making the changes.
Comment #14
sreynen commentedI lost track of this for a while, just getting back to it now.
We don't really have a process for testing group creation. Ideally that wouldn't need testing, as the UI would be very clear. It's not there yet.
In general, we don't expect people to put a lot of work into a group before it has members. Most groups just have a paragraph or two stating the purpose and I doubt many group organizers spend more than 5 or 10 minutes writing that, so it's not a big loss to just delete it. This is what we've done as long as I've been involved and this is the first case I know of where that's been a problem.
It also rarely seems important to delete a group quickly. In this case, that seemed important because the group seemed very likely to be misunderstood as some sort of community-sanctioned representation of the site. Mostly because it had the name of the site in the name of the group.
In both regards, I think this is an exceptional case that probably doesn't imply a need for more general process changes.
b-d, if you just want to create a group for testing, I think we can probably leave that in moderation forever, so long as it's very clearly marked as a group for testing purposes, to avoid confusion. Maybe a name like "Example Group" would be good, and the content probably shouldn't talk about how the site works, to avoid confusion. We have both a group and an issue queue for discussing how the site works, which you're already using for that purpose.
If you have any questions about what kind of example content would be appropriate for an example group, I'm happy to talk about that more. Or if you think you're clear on that, I think you could just go ahead and create an example group.