Re: [che-dev] Out of date Development Workflow page in Che Wiki - update

[Sun Tan <sutan@xxxxxxxxxx>]

Hello Nick,

I am currently refreshing the wiki piece by piece. My plan is to remove as much as possible content from the wiki to avoid to have too many sources of information (wiki, docs, website, readme).

About development workflow, the content will move to CONTRIBUTING.md of each project repo. Each CONTRIBUTING.md will be referred in the main eclipse/che CONTRIBUTING.md. It makes sense to go that way add new contributors would rather go to the github repo of a project than going to the wiki 

Le lun. 29 juil. 2019 à 18:05, Dave Neary <dneary@xxxxxxxxxx> a écrit :

Hi Nick,

A small suggestion: Rather than have someone figure out what version of
Che they are running to get access to the developer page, I have seen
other projects adopt a best practice of adding a (discrete) header that
says something like "The information in this page refers to Eclipse Che
7, if you are looking for information on Che 6, click here -->" - you
can then make a template and include this in pages easily. It's removing
one click for most people, and still allows others to get at the
information they need.

Just a suggestion.

Thanks,
Dave.

On 29/07/2019 10:43, Nick Boldt wrote:
> While looking for a quick guide to building Che 7 (in order to share it
> with a potential new contributor on Eclipse Mattermost) I noticed this
> morning that the Development Workflow page was horribly out of date.
>
> So I've taken a first pass at updating it to include new repos added for
> Che 7, removed since Che 6, purge the GWT-related info, and update
> dependency info (eg., gulp -> yarn).
>
> Rather than just delete the old Che 6 and earlier info, I've moved it to
> a new page, and created a new Che 7+ or Che 6- landing page:
>
> https://github.com/eclipse/che/wiki/Development-Workflow
>
> Please feel free to have a read through and fix anything else that's no
> longer accurate with respect to Che 7 development, or add more Che repos
> that I forgot to list under here:
>
> https://github.com/eclipse/che/wiki/Development-Workflow,-Che-7#repository-layout
>
> Might also be worth verifying if the selenium section is still accurate
> and if the QE checklist is the same.  Maybe we can remove the stuff
> about "flaky tests" ? 
>
> https://github.com/eclipse/che/wiki/Development-Workflow,-Che-7#how-to-run-selenium-tests
> https://github.com/eclipse/che/wiki/Checklist-of-pull-request-approval-by-Eclipse-Che-QE-team
>
> Nick
>
> --
>
> Nick Boldt
>
> Principal Software Engineer, RHCSA
>
> Productization Lead :: CodeReady Workspaces 
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>
> <https://red.ht/sig> 
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
> @ @redhatnews <https://twitter.com/redhatnews>     Red Hat
> <https://www.facebook.com/RedHatInc>
> <https://www.facebook.com/RedHatInc>
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
>
> _______________________________________________
> che-dev mailing list
> che-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/che-dev
>

--
Dave Neary - Community Architect
Open Source Program Office - Red Hat
E: dneary@xxxxxxxxxx / T: @nearyd / Ph: +1-978-799-3338
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev