You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by "bdelacretaz (via GitHub)" <gi...@apache.org> on 2023/04/20 13:17:44 UTC
[GitHub] [comdev-site] bdelacretaz commented on pull request #102: Best practice docs for PMCs, etc
bdelacretaz commented on PR #102:
URL: https://github.com/apache/comdev-site/pull/102#issuecomment-1516313840
This looks really nice and useful, thanks!
I see at least two existing pages that overlap with this new content:
* https://apache.org/foundation/how-it-works.html
* https://community.apache.org/contributors/
The first one might just need a link to this new content, which is less formal and more detailed. And also the reverse link, maybe a "See Also" section in your contributors ladder page?
The second one might be replaced by your new content? In which case I'd suggest [redirecting](https://github.com/apache/comdev-site/blob/main/static/.htaccess), so that the old URL remains valid.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [GitHub] [comdev-site] bdelacretaz commented on pull request #102: Best practice docs for PMCs, etc
Posted by rb...@rcbowen.com.
On Thu, 2023-04-20 at 13:17 +0000, bdelacretaz (via GitHub) wrote:
>
> bdelacretaz commented on PR #102:
> URL:
> https://github.com/apache/comdev-site/pull/102#issuecomment-1516313840
>
> This looks really nice and useful, thanks!
>
> I see at least two existing pages that overlap with this new
> content:
>
> * https://apache.org/foundation/how-it-works.html
Yes, the how-it-works page is useful, but very terse, and tries to cram
everything into one page, rather than segregating by audience, as I'm
trying to do. Both are useful, but I think they should like to each
other.
> * https://community.apache.org/contributors/
That page is very muddled, and I have plans to un-muddle it. I think it
tries to cover too much in one page, and also addresses several
audiences at the same time.
>
> The first one might just need a link to this new content, which is
> less formal and more detailed. And also the reverse link, maybe a
> "See Also" section in your contributors ladder page?
>
> The second one might be replaced by your new content? In which
> case I'd suggest
> [redirecting](https://github.com/apache/comdev-site/blob/main/static/
> .htaccess), so that the old URL remains valid.
My intent is that /contributors/, /committers/, and /pmc/ would each
have an index page that outlines what topics are covered in that
directory. I don't want to lose the content that is currently on
/contributors/index but I think that it might end up going other
places.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org