wiki for me but not for thee (was CFD Project Lilliput)
Magnus Ihse Bursie
magnus.ihse.bursie at oracle.com
Wed Mar 10 09:53:57 UTC 2021
On 2021-03-09 20:05, John Rose wrote:
> On Mar 9, 2021, at 10:55 AM, Magnus Ihse Bursie <magnus.ihse.bursie at oracle.com> wrote:
>> On 2021-03-09 19:11, John Rose wrote:
>>> While it would be better to use a wiki somewhere
>>> for collaborative edits, there aren’t any good options
>>> under ojn for this (due to inconvenient rules for
>>> authoring the wiki).
>> Which, while being a side-track, is really annoying. How come we cannot setup infrastructure that helps, instead of hinders, the OpenJDK community from making collaborative efforts? :-(
> The wiki rules are unfortunately specified in the oj
> rules, which themselves are unfortunately hard to
> change. (That’s my understanding; to be corrected
> by advice from those who know better.)
By "oj rules", do you mean the Bylaws?
And even if the rules are hard to change, we should make the effort to
do so. After all, the rules are not important in and of themselves --
they are there as a tool to help us achieve our common goal more easily.
>> An alternative is to create an empty branch in jdk-sandbox, add a README.md file, and edit it. This way every OpenJDK Author can contribute, changes are attributed to the right person, and you'll get a change history as well. And you get markdown code and realtime html rendering by Github.
> Yes, nice workaround! But, doesn’t the sandbox
> get cleaned sometimes?
No, definitely not. It was originally created as a mercurial variant of
the Github "personal fork" idea, but now it has more or less shifted
into a lightweight way of quickly setting up collaborative workspaces
without the need for OpenJDK formalia and ceremony.
> — John
More information about the discuss