Not sure if this is purely a documentation issue, but I wasn't sure where to submit it.
On the Community Initiative page (http://drupal.org/community-initiatives), the link "Core documentation" (http://drupal.org/node/363007) leads to an Access Denied error.
Comments
Comment #1
arianek commentedeep - i can see that unpublished page and it's um... well, i have no idea why it would have been linked to there! not sure what it *should* be linked to - going to tag this so jhodgdon sees it.
the "documentation project" link leads to http://drupal.org/community-initiatives/documentation too, which i'm not sure is too well kept... i wonder if it's worth just moving anything current into http://drupal.org/contribute/documentation and then making that link a redirect to the contribute to docs section (or a subsection of the current docs initiatives).
thanks for flagging this!
Comment #2
MGParisi commentedThis page is all sorts of messed up. It's title is "Community Initiatives" but it is rather selective in which initiatives, and I would hate to keep a list of all groups that are under that command. But "Core Documentation" is not any different then "Documentation" and the community-initiatives page seems to be a duplicate of other pages.
If I was to make the decision I would dump all of these pages into the archive and be done with it.
Comment #3
jhodgdonThat core docs link was way out of date and we have no equivalent, so I removed it.
Comment #4
jhodgdonWe don't want to get rid of the Community Initiatives section. It is used currently by Core development to discuss longer-term initiatives. I am also trying to keep the Doc sub-page there up to date with our longer term initiatives.
Comment #5
arianek commentedi didn't mean getting rid of the entire section, just the docs section there, and making the link basically a shell page that directs them to the http://drupal.org/contribute/documentation page.
Comment #6
jhodgdonI suppose we could move the whole http://drupal.org/community-initiatives/documentation section into contribute/documentation, but my reasoning for leaving it in Community Initiatives is that Community Initiatives is the established place for discussing larger initiatives relative to drupal.org infrastructure and Drupal core, so traditionally there has also been a section there for discussing larger Docs initiatives too.
I guess we could make http://drupal.org/community-initiatives/documentation into a stub page saying "Docs initiatives are discussed on (link). It migth make contribute to doc more coherent... Thoughts?
Comment #7
arianek commentedOk, I'm totally torn thinking about this again. I just seems like it's confusing as far as where *docs team* should look. But having a section in the main CI area does seem important from the perspective of the wider community...
Comment #8
lisarex commented@arianek What you propose, a stub page in the main CI that takes folks to the right place for docs, sounds good to me.
Comment #9
lisarex commentedOops that was @jhodgdon that suggested that.
This section is one of those that will be audited. It's an important one so I'll do it myself if no other volunteers step up...
Comment #10
arianek commentedit was me (comment #1) :-p
i just started waffling on whether it's a bad idea to make docs too separate from the other initiatives by doing that. it's nice to treat it as part of the work rather than a subset. ;) but it is just a bit difficult having the content spread out, so if you can think of a better way to manage that, all ears!
Comment #11
jhodgdonI am ambivalent, as long as we have cross-linking.
Comment #12
jhodgdonThe orginal issue here was long ago resolved, and the larger discussion is outdated, so closing this issue.