Hi Dale,
Cool … will have to investigate … think this would be good for the Flex project
too ;-)
Regarding the build system … what is the projects general opinion on a Maven
build? I know that Ant and Gradle are a lot more flexible as Maven, but I think
it is a good thing that Maven is this strict, as it forces the developers to
address structural issues instead of using workarounds. Especially in
Open-Source projects with a lot of different levels of build system expertise I
usually always had problems with non Maven builds. But this is just a general
question without having seen the current state … just managing to reach the
summit of that pile of work you find when coming back from a 1,5 week leave ;-)
Chris
Am 24.05.17, 15:33 schrieb "Dale LaBossiere" <dml.apa...@gmail.com>:
Yeah, the new "GitHub as the main repo” config came up in John’s incubator
talk @ ApacheCon. Pretty sure OpenWisk was one of the projects using it.
Don’t recall the other incubator project that was gushing over it. As you
might expect there was a LOT of interest in it.
Consider this a personal invitation to help cleanup the build system :-)
— Dale
> On May 23, 2017, at 4:26 PM, Christofer Dutz <christofer.d...@c-ware.de>
wrote:
>
> Hi,
>
> I’m just asking, because the Flex project started with SVN and we
migrated to ASF GIT. Now we have the GitHub mirrors setup and can process Pull
requests etc. But it’s not our main repo. Our main repo is the ASF one.
>
> Are you sure you can really use the Merge button on pull requests?
Wouldn’t this require deeper access to Github. We currently do things by
sending commands to close pull requests etc. in the commit messages. So, if we
say: “closes #238” the ASF bots close the pull requests for us. If things have
changed, this might be interesting for the Flex Project too.
>
> In general, these types of migrations are really easy … just create one
of the Infra tickets and things happen automatically. I think they even have
issue templates for things like this.
>
> And regarding help … The sort of thing I do quite a lot in my paid job
and here at Apache, is build systems cleanup … my speciality are Maven
migrations. Reading other emails it looked a little complicated with your
current Gradle setup … want any help in that … just ask ;-)
>
> Looking forward do digging deeper into this (
>
> Chris
>
> Am 23.05.17, 17:13 schrieb "Dale LaBossiere" <dml.apa...@gmail.com>:
>
> 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
<christofer.d...@c-ware.de> 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" <chanskw...@gmail.com>:
>>
>> 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 <johndam...@apache.org>
>> 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 <dml.apa...@gmail.com>
>>> 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
>>>
>>
>>
>
>
>
