Hi Christofer,  

Sorry I didn’t manage to catch up with you @ ApacheCon following your SCADA 
talk and mention of interest in Edgent.  We’re greatly interested in your 
interest/feedback!

Re git, Edgent(Quarks) was a GitHub based project prior to donation/incubating 
@ ASF.  The Apache Edgent ASF project was created with SVN as the main repo 
with an ASF git repo mirror and a read-only mirror of that to GitHub — 
apparently standard ASF fare at the time for those wanting to use git/github.  
We promote using the gitflow model of forking the GitHub mirror for 
committing/creating and reviewing PRs.  Then committers use git to merge the PR 
to the ASF git repo - ugh.

The proposal is to convert to the newly supported “GitHub as the main repo” 
approach.  Then we’ll be able to fully use the normal gitflow model including 
the Merge button on the PR’s page!  And use of GitHub Issues instead of JIRA.

As I understand it, the repo switch issue is (easily?) handled by generating an 
infra request once the project decides to head in that direction.

— Dale


> On May 23, 2017, at 10:29 AM, Christofer Dutz <[email protected]> 
> wrote:
> 
> Hi guys,
> 
> This is the first mail I got after signing up ;-)
> Fascinating project you have here … guess I will hang around quite some time 
> in the (hopefully) near future.
> 
> Guess I might be able to help you with this GIT topic. Are you thinking of 
> switching to GIT in general from SVN? Or do you want to commit to GitHub and 
> hope for this to get synced back to the ASF SVN?
> 
> Chris
> 
> 
> 
> Am 23.05.17, 15:50 schrieb "Samantha Chan" <[email protected]>:
> 
>    Hi Dale,
> 
>    +1!  I would like to use Github as a primary repo.
>    I think it will make it easier for people to discover, adopt and contribute
>    code back. Using Github issues vs Jira also seems like a good idea.  We can
>    have everything at a single point of entry.
> 
>    Samantha
> 
> 
> 
>    On Wed, May 17, 2017 at 2:02 PM, John D. Ament <[email protected]>
>    wrote:
> 
>> Assuming we have a CSV type of dump, it seems like a client could be
>> written to do the import.
>> 
>> http://stackoverflow.com/questions/31125655/is-there-a-
>> way-to-import-jira-issues-to-github
>> 
>> John
>> 
>> On Wed, May 17, 2017 at 1:58 PM Dale LaBossiere <[email protected]>
>> wrote:
>> 
>>> Hey all,
>>> 
>>> Today @ApacheCon I learned that infra now supports GitHub as a primary
>>> repo (in contrast to our GitHub mirror of svn).  What would switching buy
>>> us?   The Merge button! :-)  and use of GitHub issues.
>>> 
>>> One roadbump, apparently the migration of JIRA issues to GitHub isn’t
>>> automated.  At least one group with a something like 100 JIRAs just did
>> it
>>> all by hand.  (don’t know if that was a total of 100 open/closed or just
>>> open).  In any case that’s something to better understand.
>>> 
>>> What do you think?
>>> 
>>> — Dale
>> 
> 
> 

Reply via email to