Hi Carsten,
I copy your answer to the user ML, as I guess you expected to send there.
Jacques
Le 11/05/2020 à 12:45, Carsten Schinzer a écrit :
Hello,
I was curious about the move to Git and happy this is going to be the solution finally. I do expect that therefore a good part of the build
automation had to be revised.
I am planning a couple of private modules and need to understand how that is now embedded into the build automation based upon Git instead of SVN
anyways.
I am also planning to use GitLab pipelines for testing on my modules and am
curious how this is solved.
I can certainly offer to align my learning on these topics with the Community days and watch out for documentation that is outdated in this
regard and track a "requires update" list.
I seem to have lost my CWIKI credentials, but will set them up in time before
the event.
Looking forward
Carsten
Am Mo., 11. Mai 2020 um 11:20 Uhr schrieb Jacques Le Roux <[email protected]
<mailto:[email protected]>>:
Thanks Devanshu,
After our move to Git we have finally cleaned our site from information
referring to Svn, and that's good.
But there is still much such info in the wiki and it can be confusing.
I suggest that we concentrate much of our efforts during this Community Day
to clean the wiki.
We can adapt to Git and keep in wiki when needed, or move in Attic under a specific
"Subversion" page when really too deprecated.
I know, for most of us, it's not as easy as coding with Git and GitHub. But
Confluence now also easily allows to share tasks and merge when needed.
We should not hesitate to prune much, nothing worse than obsolete and
confusing documentation
I hope everyone will help, it's really long due :)
Thanks
Jacques
Le 11/05/2020 à 06:40, Devanshu Vyas a écrit :
> Hello all,
>
> We are back with OFBiz Community Days, hope you are excited too! :-)
> The community days are organized once per quarter so a total of four (4)
> events throughout the year.
>
> We are having a sequence of 5 days that form the Community Days. This
> extends the time frame and gives people more flexibility to contribute.
> So, this month our Community Days will be from *22nd – 26th May 2020*.
>
> If you are new to the concept of Community Days then please take a look at
> the following wiki pages:
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days
>
https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days+Dates
>
> This is such an event where anyone can participate (and we would like to
> encourage as many people as possible to do so)
>
> If there is an OFBiz task or particular area that you would like to work
on
> then please see if you can set aside some time over the next few days to
do
> it. (Even an hour will help!)
>
> Remember that you do not have to work on it alone, our Community Days are
> also a chance to collaborate with others in the community.
>
> Our Community Days are not only coding related, but we would also like to
> do some tidy up of our wiki and our project documentation.
>
> *Testing, Review and Committing Patches*
> Testing and applying patches is always an important area. Many
contributors
> from the community have provided patches for bugs and improvements but
> before committing them we need to test to them.
>
> Patches can become out of date very quickly meaning that if they are not
> tested early enough then they can miss out on being included. We have a
> large number of patches available so this could be a good opportunity for
> test, review and commit.
>
> *Documentation*
> We know that our current documentation could be a whole lot better so any
> contribution that helps us improve it is welcome.
>
> *Jira Sprint*
> I will create a Jira sprint "OFBiz Community Day (May 2020)" so please add
> any Jira tasks when you are working on it.
> This Jira Sprint helps us track and report on the work done during the
> Community Days so please try to make sure your work is included.
> To set the sprint on an existing issue, simply click on the "Edit" option
> on the issue and select the sprint field.
>
> We should add the Sprint in all the cases:
> 1.) If we create a ticket we should add it.
> 2.) If we start working on an existing ticket (adding patch or closing it
> after a commit) we should add sprint if it is missing.
>
> Basically adding Sprint will make sure the contribution will be counted in
> OFBiz community days event, which is from 22nd – 26th May.
> At the end of May's OFBiz Community day i.e. after 26th May, this will
help
> us in reporting.
>
> *OFBiz Slack Channel*
> If you haven't already taken a look, our OFBiz Slack channel is available
> all the time but can be especially useful when collaborating during our
> Community Days event. Please join our room using the link below:
> https://s.apache.org/ofbiz-slack-channel
>
> To chat with users and developers of Apache OFBiz. Please create a Slack
> account using this invite link <https://s.apache.org/slack-invite> and
join
> the *#ofbiz channel*. <https://s.apache.org/ofbiz-slack-channel> Please do
> *not* ask OFBiz questions/discussion in the #general channel.
>
> Let's all collaborate to improve OFBiz, have fun and enjoy working
together.
>
> Thanks & Regards,
> Devanshu Vyas.
