Now that I have cooled down a bit, let me try to find the middle ground. These are the steps I have in mind:
* We go with hugo/markdown * We (myself and anyone that wants to step in) evaluate every document on the website and either convert it or not. * When we have questions, we contact this list or create issues in the new GitHub site * Every step we take will be visible in Git and immediately on https:// testuser:[email protected]/eclipse * When we encounter a dynamic page (acknowledgment, plan, whatever) we figure out what needs to be done * When the site is ready, we have a list of pages NOT included in the new site (we don't add anything). This list will be brought to the PMC * After PMC approval we go live Cheers, Wim On Tue, Mar 30, 2021 at 4:23 PM Wim Jongman <[email protected]> wrote: > > > >> Sorry about this being mistrusting and bureaucratic; but on the other >> hand this is sometimes useful to ensure that resources and energy is >> optimized and that value/risk ratio is good. >> > > I rest my case. 😉😂 > > > >> >> I agree many documents can probably be discarded, and a cleanup would >> help in migrating to a new website without too much effort IMO. I think you >> can already submit Gerrit patches suggesting to drop some documents and get >> PMC to agree on removal. >> > > Well, my plan was to import every relevant document from our website > manually, update the content whilst converting it into a proper markdown > document and discard around probably 71,2% of junk this way. > > Creating Gerrits to delete content from the old website is not the > holistic approach I'm aiming for (leads to dead links and forces to repair > it in phphtml) > > So I pass for your approach. Let me know if you want me to continue with > my plan. > > Cheers, > > Wim > > > >
_______________________________________________ platform-dev mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
