Re: Document our WIP

[Gurjeet Singh]

On Wed, Mar 31, 2021 at 11:17 AM Leo Famulari <leo@famulari.name> wrote:
>
> Yeah, I agree that it's hard to learn about "what's cooking" when you
> first arrive at the mailing lists.
>
> It's true that wikis tend to get out of date, but I think that it won't
> be too bad for this use case. At least, it won't be worse than the
> mailing lists, for newcomers who want to know about longer-term efforts
> like the GNOME upgrade.

May I suggest the Postgres project's model of maintaining a Todo list
as a Wiki page, which shows the readers what they can contribute to,
links to past discussions on the items, etc. This way even if the
progress on a patch stops, someone, at some point in future can revive
it based on the info in the Wiki. Of course, it'd be useless unless it
is regularly updated.

Also, it must be discoverable.  Postgres, for example, links it as
follows, and the folks, usually who specialize in community outreach,
regularly update it [6]. This model has worked quite well for them, so
I think it's a good model to try to emulate.

Postgres home page [1] > Community  [2] > Wiki [3] > Contributor Info
> Developer Info [4] > Todo list [5].

[1]: https://www.postgresql.org/
[2]: https://www.postgresql.org/community/
[3]: https://wiki.postgresql.org/wiki/Main_Page
[4]: https://wiki.postgresql.org/wiki/Development_information
[5]: https://wiki.postgresql.org/wiki/Todo
[6]: https://wiki.postgresql.org/index.php?title=Todo&action=history

Best regards,
--
Gurjeet Singh http://gurjeet.singh.im/