On Tue, Mar 30, 2021 at 1:50 PM Wim Jongman <[email protected]> wrote:

> Dude, you cannot drop this bomb right now. I have spent 5 full working
> days to get this party started. And now you come with an "opinion"?
> I have communicated very early that I was working on bringing the website
> to Hugo which has full support from the foundation.
>

I can't support that "big bang" change without a detailed and
incremental/iterative plan. Good thing is that you don't need my support:
the www.eclipse.org/eclipse website belongs to the Eclipse Top Level
Project and that needs PMC approval.

Although I understand the frustration of things being slown down by my
critical mind, I think the fact that you spent time on it doesn't suffice
to make it a project decision. All that seems still quite experimental to
me (experimental in the sense of "towards better outcome" nor as "bad") and
I'm yet to see some insurance that the important content (eg some
acknowledgements, plans and so on) are properly preserved with 1. the move
of the repo to GitHub and 2. usage of Hugo. So far, I didn't see anything
that audits which documents are to move and which ones aren't, nor some
plan regarding necessary documents that are made of HTML (and maybe even
PHP) would move to Hugo. Does that mean someone will have to translate all
that from HTML to markdown?
So what about existing documents on
https://git.eclipse.org/c/www.eclipse.org/eclipse.git/tree/ ? Have you
discussed with PMC which ones can be discarded and which ones need to
remain? And what would be the strategy for the remaining ones?
This concern is what makes me think that a 1st iteration moving the website
to GitHub would allow to close a part of the discussion and already deliver
some added-value without too much risk; and then the usage of Hugo could be
further and more efficiently discussed.
_______________________________________________
platform-dev mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Reply via email to