You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by Christofer Dutz <ch...@c-ware.de> on 2017/11/07 08:30:07 UTC
Creating a new git repo for the Edgent project
Hi John,
we have just migrated the entire Edgent project to a Maven build and would now like to split out the samples. For that we would require a “edgent-samples” git repo. I was told to contact you in order to create such a repo.
Could you please do that for us?
Chris
Re: Creating a new git repo for the Edgent project
Posted by Dale LaBossiere <dm...@gmail.com>.
Thanks! I’ll check it out.
— Dale
> On Nov 21, 2017, at 6:53 AM, Christofer Dutz <ch...@c-ware.de> wrote:
> ...
> So, I just managed to perform the split. I initialized the new repo with the content of the samples directory. And this should now be available in the develop branch there.
> Currently the main repo still contains the samples directory. I think after verifying the new repo and confirming that all is good, we can then delete the directory in the main repo.
>
> Please checkout the new repo and check if everything is ok.
Re: Creating a new git repo for the Edgent project
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi all,
So, I just managed to perform the split. I initialized the new repo with the content of the samples directory. And this should now be available in the develop branch there.
Currently the main repo still contains the samples directory. I think after verifying the new repo and confirming that all is good, we can then delete the directory in the main repo.
Please checkout the new repo and check if everything is ok.
Chris
Am 21.11.17, 10:01 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Great ... Thank you, l'll Handle filling it with life as soon as possible.
Chris
Outlook for Android<https://aka.ms/ghei36> herunterladen
________________________________
From: John D. Ament <jo...@gmail.com>
Sent: Tuesday, November 21, 2017 1:05:44 AM
To: dev@edgent.apache.org
Subject: Re: Creating a new git repo for the Edgent project
It now exists:
https://git-wip-us.apache.org/repos/asf/incubator-edgent-samples.git
And look forward to seeing it on github tomorrow some time.
On Mon, Nov 20, 2017 at 10:53 AM John D. Ament <jo...@apache.org>
wrote:
> I have submitted the request.
>
>
> On Mon, Nov 20, 2017 at 9:44 AM Dale LaBossiere <dm...@gmail.com>
> wrote:
>
>> I don’t think a formal vote is required. Anyone who might have had an
>> opinion has had ample opportunity to express it.
>> So, the informal tally is two +1 (you and me) and no -1.
>>
>> So, John, please move forward with creating a repo for the samples.
>>
>> Thanks!
>> — Dale
>>
>>
>> > On Nov 12, 2017, at 8:34 AM, Christofer Dutz <ch...@c-ware.de>
>> wrote:
>> >
>> > Sooo … what’s the current state?
>> >
>> > Do we need a vote on this to document the desire to create a new repo?
>> >
>> > Chris
>> >
>> > Am 08.11.17, 06:16 schrieb "Christofer Dutz" <christofer.dutz@c-ware.de
>> >:
>> >
>> > Hi all,
>> >
>> > well there are several reasons, why I think separating the samples
>> from the framework is a good idea.
>> >
>> > 1) It makes the repo a lot bigger and as you said overwhelming
>> > 2) Usually people want to use Edgent and only a certain percentage
>> also want to contribute, build-time, complexity-to-setup,
>> complexity-to-understand etc. could scare people
>> > 3) Usually Samples are a sort of playground … one that has to be
>> maintained. Would be unfortunate to have to wait to clean up sample code
>> and keep us from releasing.
>> > 4) To be on the safe side, we should have to do the same duplication
>> to build the samples with java7 or java8 … usually a user just wants to
>> build it for one.
>> >
>> > Right now, the way the samples are included, when doing a full
>> build, the samples would always be built for java7 as this is the last
>> profile defined.
>> >
>> > But that’s just my opinion.
>> >
>> > Chris
>> >
>> >
>> > Am 07.11.17, 19:00 schrieb "Dale LaBossiere" <dm...@gmail.com>:
>> >
>> > Let’s see what Chris’ thoughts are.
>> >
>> > Another aspect of the separation is that importing the full
>> Edgent sources into an IDE workspace, just to get the samples, can be a bit
>> overwhelming (with regards to the number of projects present). We could
>> tell users to deselect all but the samples tree in say the Eclipse import
>> wizard. Just seems cleaner / easier for a user if we can avoid that detail.
>> >
>> > — Dale
>> >
>> >> On Nov 7, 2017, at 12:16 PM, John D. Ament <jo...@apache.org>
>> wrote:
>> >>
>> >> At the end of the day, for me, its whatever the podling thinks it
>> needs to
>> >> be successful. I can only give tips based on what I have seen work.
>> >>
>> >> Just don't forget that having separate samples means that they can out
>> of
>> >> date pretty quickly.
>> >
>> >
>> >
>> >
>> >
>>
>>
Re: Creating a new git repo for the Edgent project
Posted by Christofer Dutz <ch...@c-ware.de>.
Great ... Thank you, l'll Handle filling it with life as soon as possible.
Chris
Outlook for Android<https://aka.ms/ghei36> herunterladen
________________________________
From: John D. Ament <jo...@gmail.com>
Sent: Tuesday, November 21, 2017 1:05:44 AM
To: dev@edgent.apache.org
Subject: Re: Creating a new git repo for the Edgent project
It now exists:
https://git-wip-us.apache.org/repos/asf/incubator-edgent-samples.git
And look forward to seeing it on github tomorrow some time.
On Mon, Nov 20, 2017 at 10:53 AM John D. Ament <jo...@apache.org>
wrote:
> I have submitted the request.
>
>
> On Mon, Nov 20, 2017 at 9:44 AM Dale LaBossiere <dm...@gmail.com>
> wrote:
>
>> I don’t think a formal vote is required. Anyone who might have had an
>> opinion has had ample opportunity to express it.
>> So, the informal tally is two +1 (you and me) and no -1.
>>
>> So, John, please move forward with creating a repo for the samples.
>>
>> Thanks!
>> — Dale
>>
>>
>> > On Nov 12, 2017, at 8:34 AM, Christofer Dutz <ch...@c-ware.de>
>> wrote:
>> >
>> > Sooo … what’s the current state?
>> >
>> > Do we need a vote on this to document the desire to create a new repo?
>> >
>> > Chris
>> >
>> > Am 08.11.17, 06:16 schrieb "Christofer Dutz" <christofer.dutz@c-ware.de
>> >:
>> >
>> > Hi all,
>> >
>> > well there are several reasons, why I think separating the samples
>> from the framework is a good idea.
>> >
>> > 1) It makes the repo a lot bigger and as you said overwhelming
>> > 2) Usually people want to use Edgent and only a certain percentage
>> also want to contribute, build-time, complexity-to-setup,
>> complexity-to-understand etc. could scare people
>> > 3) Usually Samples are a sort of playground … one that has to be
>> maintained. Would be unfortunate to have to wait to clean up sample code
>> and keep us from releasing.
>> > 4) To be on the safe side, we should have to do the same duplication
>> to build the samples with java7 or java8 … usually a user just wants to
>> build it for one.
>> >
>> > Right now, the way the samples are included, when doing a full
>> build, the samples would always be built for java7 as this is the last
>> profile defined.
>> >
>> > But that’s just my opinion.
>> >
>> > Chris
>> >
>> >
>> > Am 07.11.17, 19:00 schrieb "Dale LaBossiere" <dm...@gmail.com>:
>> >
>> > Let’s see what Chris’ thoughts are.
>> >
>> > Another aspect of the separation is that importing the full
>> Edgent sources into an IDE workspace, just to get the samples, can be a bit
>> overwhelming (with regards to the number of projects present). We could
>> tell users to deselect all but the samples tree in say the Eclipse import
>> wizard. Just seems cleaner / easier for a user if we can avoid that detail.
>> >
>> > — Dale
>> >
>> >> On Nov 7, 2017, at 12:16 PM, John D. Ament <jo...@apache.org>
>> wrote:
>> >>
>> >> At the end of the day, for me, its whatever the podling thinks it
>> needs to
>> >> be successful. I can only give tips based on what I have seen work.
>> >>
>> >> Just don't forget that having separate samples means that they can out
>> of
>> >> date pretty quickly.
>> >
>> >
>> >
>> >
>> >
>>
>>
Re: Creating a new git repo for the Edgent project
Posted by "John D. Ament" <jo...@gmail.com>.
It now exists:
https://git-wip-us.apache.org/repos/asf/incubator-edgent-samples.git
And look forward to seeing it on github tomorrow some time.
On Mon, Nov 20, 2017 at 10:53 AM John D. Ament <jo...@apache.org>
wrote:
> I have submitted the request.
>
>
> On Mon, Nov 20, 2017 at 9:44 AM Dale LaBossiere <dm...@gmail.com>
> wrote:
>
>> I don’t think a formal vote is required. Anyone who might have had an
>> opinion has had ample opportunity to express it.
>> So, the informal tally is two +1 (you and me) and no -1.
>>
>> So, John, please move forward with creating a repo for the samples.
>>
>> Thanks!
>> — Dale
>>
>>
>> > On Nov 12, 2017, at 8:34 AM, Christofer Dutz <ch...@c-ware.de>
>> wrote:
>> >
>> > Sooo … what’s the current state?
>> >
>> > Do we need a vote on this to document the desire to create a new repo?
>> >
>> > Chris
>> >
>> > Am 08.11.17, 06:16 schrieb "Christofer Dutz" <christofer.dutz@c-ware.de
>> >:
>> >
>> > Hi all,
>> >
>> > well there are several reasons, why I think separating the samples
>> from the framework is a good idea.
>> >
>> > 1) It makes the repo a lot bigger and as you said overwhelming
>> > 2) Usually people want to use Edgent and only a certain percentage
>> also want to contribute, build-time, complexity-to-setup,
>> complexity-to-understand etc. could scare people
>> > 3) Usually Samples are a sort of playground … one that has to be
>> maintained. Would be unfortunate to have to wait to clean up sample code
>> and keep us from releasing.
>> > 4) To be on the safe side, we should have to do the same duplication
>> to build the samples with java7 or java8 … usually a user just wants to
>> build it for one.
>> >
>> > Right now, the way the samples are included, when doing a full
>> build, the samples would always be built for java7 as this is the last
>> profile defined.
>> >
>> > But that’s just my opinion.
>> >
>> > Chris
>> >
>> >
>> > Am 07.11.17, 19:00 schrieb "Dale LaBossiere" <dm...@gmail.com>:
>> >
>> > Let’s see what Chris’ thoughts are.
>> >
>> > Another aspect of the separation is that importing the full
>> Edgent sources into an IDE workspace, just to get the samples, can be a bit
>> overwhelming (with regards to the number of projects present). We could
>> tell users to deselect all but the samples tree in say the Eclipse import
>> wizard. Just seems cleaner / easier for a user if we can avoid that detail.
>> >
>> > — Dale
>> >
>> >> On Nov 7, 2017, at 12:16 PM, John D. Ament <jo...@apache.org>
>> wrote:
>> >>
>> >> At the end of the day, for me, its whatever the podling thinks it
>> needs to
>> >> be successful. I can only give tips based on what I have seen work.
>> >>
>> >> Just don't forget that having separate samples means that they can out
>> of
>> >> date pretty quickly.
>> >
>> >
>> >
>> >
>> >
>>
>>
Re: Creating a new git repo for the Edgent project
Posted by "John D. Ament" <jo...@apache.org>.
I have submitted the request.
On Mon, Nov 20, 2017 at 9:44 AM Dale LaBossiere <dm...@gmail.com>
wrote:
> I don’t think a formal vote is required. Anyone who might have had an
> opinion has had ample opportunity to express it.
> So, the informal tally is two +1 (you and me) and no -1.
>
> So, John, please move forward with creating a repo for the samples.
>
> Thanks!
> — Dale
>
>
> > On Nov 12, 2017, at 8:34 AM, Christofer Dutz <ch...@c-ware.de>
> wrote:
> >
> > Sooo … what’s the current state?
> >
> > Do we need a vote on this to document the desire to create a new repo?
> >
> > Chris
> >
> > Am 08.11.17, 06:16 schrieb "Christofer Dutz" <christofer.dutz@c-ware.de
> >:
> >
> > Hi all,
> >
> > well there are several reasons, why I think separating the samples
> from the framework is a good idea.
> >
> > 1) It makes the repo a lot bigger and as you said overwhelming
> > 2) Usually people want to use Edgent and only a certain percentage
> also want to contribute, build-time, complexity-to-setup,
> complexity-to-understand etc. could scare people
> > 3) Usually Samples are a sort of playground … one that has to be
> maintained. Would be unfortunate to have to wait to clean up sample code
> and keep us from releasing.
> > 4) To be on the safe side, we should have to do the same duplication
> to build the samples with java7 or java8 … usually a user just wants to
> build it for one.
> >
> > Right now, the way the samples are included, when doing a full build,
> the samples would always be built for java7 as this is the last profile
> defined.
> >
> > But that’s just my opinion.
> >
> > Chris
> >
> >
> > Am 07.11.17, 19:00 schrieb "Dale LaBossiere" <dm...@gmail.com>:
> >
> > Let’s see what Chris’ thoughts are.
> >
> > Another aspect of the separation is that importing the full
> Edgent sources into an IDE workspace, just to get the samples, can be a bit
> overwhelming (with regards to the number of projects present). We could
> tell users to deselect all but the samples tree in say the Eclipse import
> wizard. Just seems cleaner / easier for a user if we can avoid that detail.
> >
> > — Dale
> >
> >> On Nov 7, 2017, at 12:16 PM, John D. Ament <jo...@apache.org>
> wrote:
> >>
> >> At the end of the day, for me, its whatever the podling thinks it needs
> to
> >> be successful. I can only give tips based on what I have seen work.
> >>
> >> Just don't forget that having separate samples means that they can out
> of
> >> date pretty quickly.
> >
> >
> >
> >
> >
>
>
Re: Creating a new git repo for the Edgent project
Posted by Dale LaBossiere <dm...@gmail.com>.
I don’t think a formal vote is required. Anyone who might have had an opinion has had ample opportunity to express it.
So, the informal tally is two +1 (you and me) and no -1.
So, John, please move forward with creating a repo for the samples.
Thanks!
— Dale
> On Nov 12, 2017, at 8:34 AM, Christofer Dutz <ch...@c-ware.de> wrote:
>
> Sooo … what’s the current state?
>
> Do we need a vote on this to document the desire to create a new repo?
>
> Chris
>
> Am 08.11.17, 06:16 schrieb "Christofer Dutz" <ch...@c-ware.de>:
>
> Hi all,
>
> well there are several reasons, why I think separating the samples from the framework is a good idea.
>
> 1) It makes the repo a lot bigger and as you said overwhelming
> 2) Usually people want to use Edgent and only a certain percentage also want to contribute, build-time, complexity-to-setup, complexity-to-understand etc. could scare people
> 3) Usually Samples are a sort of playground … one that has to be maintained. Would be unfortunate to have to wait to clean up sample code and keep us from releasing.
> 4) To be on the safe side, we should have to do the same duplication to build the samples with java7 or java8 … usually a user just wants to build it for one.
>
> Right now, the way the samples are included, when doing a full build, the samples would always be built for java7 as this is the last profile defined.
>
> But that’s just my opinion.
>
> Chris
>
>
> Am 07.11.17, 19:00 schrieb "Dale LaBossiere" <dm...@gmail.com>:
>
> Let’s see what Chris’ thoughts are.
>
> Another aspect of the separation is that importing the full Edgent sources into an IDE workspace, just to get the samples, can be a bit overwhelming (with regards to the number of projects present). We could tell users to deselect all but the samples tree in say the Eclipse import wizard. Just seems cleaner / easier for a user if we can avoid that detail.
>
> — Dale
>
>> On Nov 7, 2017, at 12:16 PM, John D. Ament <jo...@apache.org> wrote:
>>
>> At the end of the day, for me, its whatever the podling thinks it needs to
>> be successful. I can only give tips based on what I have seen work.
>>
>> Just don't forget that having separate samples means that they can out of
>> date pretty quickly.
>
>
>
>
>
Re: Creating a new git repo for the Edgent project
Posted by Christofer Dutz <ch...@c-ware.de>.
Sooo … what’s the current state?
Do we need a vote on this to document the desire to create a new repo?
Chris
Am 08.11.17, 06:16 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi all,
well there are several reasons, why I think separating the samples from the framework is a good idea.
1) It makes the repo a lot bigger and as you said overwhelming
2) Usually people want to use Edgent and only a certain percentage also want to contribute, build-time, complexity-to-setup, complexity-to-understand etc. could scare people
3) Usually Samples are a sort of playground … one that has to be maintained. Would be unfortunate to have to wait to clean up sample code and keep us from releasing.
4) To be on the safe side, we should have to do the same duplication to build the samples with java7 or java8 … usually a user just wants to build it for one.
Right now, the way the samples are included, when doing a full build, the samples would always be built for java7 as this is the last profile defined.
But that’s just my opinion.
Chris
Am 07.11.17, 19:00 schrieb "Dale LaBossiere" <dm...@gmail.com>:
Let’s see what Chris’ thoughts are.
Another aspect of the separation is that importing the full Edgent sources into an IDE workspace, just to get the samples, can be a bit overwhelming (with regards to the number of projects present). We could tell users to deselect all but the samples tree in say the Eclipse import wizard. Just seems cleaner / easier for a user if we can avoid that detail.
— Dale
> On Nov 7, 2017, at 12:16 PM, John D. Ament <jo...@apache.org> wrote:
>
> At the end of the day, for me, its whatever the podling thinks it needs to
> be successful. I can only give tips based on what I have seen work.
>
> Just don't forget that having separate samples means that they can out of
> date pretty quickly.
Re: Creating a new git repo for the Edgent project
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi all,
well there are several reasons, why I think separating the samples from the framework is a good idea.
1) It makes the repo a lot bigger and as you said overwhelming
2) Usually people want to use Edgent and only a certain percentage also want to contribute, build-time, complexity-to-setup, complexity-to-understand etc. could scare people
3) Usually Samples are a sort of playground … one that has to be maintained. Would be unfortunate to have to wait to clean up sample code and keep us from releasing.
4) To be on the safe side, we should have to do the same duplication to build the samples with java7 or java8 … usually a user just wants to build it for one.
Right now, the way the samples are included, when doing a full build, the samples would always be built for java7 as this is the last profile defined.
But that’s just my opinion.
Chris
Am 07.11.17, 19:00 schrieb "Dale LaBossiere" <dm...@gmail.com>:
Let’s see what Chris’ thoughts are.
Another aspect of the separation is that importing the full Edgent sources into an IDE workspace, just to get the samples, can be a bit overwhelming (with regards to the number of projects present). We could tell users to deselect all but the samples tree in say the Eclipse import wizard. Just seems cleaner / easier for a user if we can avoid that detail.
— Dale
> On Nov 7, 2017, at 12:16 PM, John D. Ament <jo...@apache.org> wrote:
>
> At the end of the day, for me, its whatever the podling thinks it needs to
> be successful. I can only give tips based on what I have seen work.
>
> Just don't forget that having separate samples means that they can out of
> date pretty quickly.
Re: Creating a new git repo for the Edgent project
Posted by Dale LaBossiere <dm...@gmail.com>.
Let’s see what Chris’ thoughts are.
Another aspect of the separation is that importing the full Edgent sources into an IDE workspace, just to get the samples, can be a bit overwhelming (with regards to the number of projects present). We could tell users to deselect all but the samples tree in say the Eclipse import wizard. Just seems cleaner / easier for a user if we can avoid that detail.
— Dale
> On Nov 7, 2017, at 12:16 PM, John D. Ament <jo...@apache.org> wrote:
>
> At the end of the day, for me, its whatever the podling thinks it needs to
> be successful. I can only give tips based on what I have seen work.
>
> Just don't forget that having separate samples means that they can out of
> date pretty quickly.
Re: Creating a new git repo for the Edgent project
Posted by "John D. Ament" <jo...@apache.org>.
At the end of the day, for me, its whatever the podling thinks it needs to
be successful. I can only give tips based on what I have seen work.
Just don't forget that having separate samples means that they can out of
date pretty quickly.
John
On Tue, Nov 7, 2017 at 12:10 PM Dale LaBossiere <dm...@gmail.com>
wrote:
> Perhaps additional discussion is warranted.
>
> A goal has been to make it easier for folks to get started using Edgent as
> opposed to being builders/developers of Edgent (hence the distribution of
> Edgent jars to maven central).
>
> Being able to easily get the sample sources separate from “Edgent” seems
> right to me. Yeah, we really don’t need to release a separate sample
> sources bundle to achieve that (and not “releasing” samples makes life
> easier for us). If the samples are in their own git/github repo then we
> can just point users there and they can easily download/clone.
>
> So, I guess I’m still a proponent of a separate repo but now not doing a
> release / separate source bundle of them. Make sense?
>
> — Dale
>
>
> > On Nov 7, 2017, at 10:40 AM, John D. Ament <jo...@apache.org>
> wrote:
> >
> > Well, its not an issue to include samples in the main source. You can
> > release it all together. You can also release it independently, but
> > typically sample repos aren't released. Its up to you guys. I'm of the
> > opinion that if you have a samples/examples repo it shouldn't get
> > released. You may want to tag it for a specific release so that others
> can
> > reference it.
> >
> > By not releasing a sample repo, you can include incompatible dependencies
> > and not have to worry (just make sure you're being clear about it in the
> > repo's readme).
> >
> > If you want, you can also just exclude the samples from the release
> source.
> >
> > I've seen projects do all three.
>
>
Re: Creating a new git repo for the Edgent project
Posted by Dale LaBossiere <dm...@gmail.com>.
Perhaps additional discussion is warranted.
A goal has been to make it easier for folks to get started using Edgent as opposed to being builders/developers of Edgent (hence the distribution of Edgent jars to maven central).
Being able to easily get the sample sources separate from “Edgent” seems right to me. Yeah, we really don’t need to release a separate sample sources bundle to achieve that (and not “releasing” samples makes life easier for us). If the samples are in their own git/github repo then we can just point users there and they can easily download/clone.
So, I guess I’m still a proponent of a separate repo but now not doing a release / separate source bundle of them. Make sense?
— Dale
> On Nov 7, 2017, at 10:40 AM, John D. Ament <jo...@apache.org> wrote:
>
> Well, its not an issue to include samples in the main source. You can
> release it all together. You can also release it independently, but
> typically sample repos aren't released. Its up to you guys. I'm of the
> opinion that if you have a samples/examples repo it shouldn't get
> released. You may want to tag it for a specific release so that others can
> reference it.
>
> By not releasing a sample repo, you can include incompatible dependencies
> and not have to worry (just make sure you're being clear about it in the
> repo's readme).
>
> If you want, you can also just exclude the samples from the release source.
>
> I've seen projects do all three.
Re: Creating a new git repo for the Edgent project
Posted by "John D. Ament" <jo...@apache.org>.
Well, its not an issue to include samples in the main source. You can
release it all together. You can also release it independently, but
typically sample repos aren't released. Its up to you guys. I'm of the
opinion that if you have a samples/examples repo it shouldn't get
released. You may want to tag it for a specific release so that others can
reference it.
By not releasing a sample repo, you can include incompatible dependencies
and not have to worry (just make sure you're being clear about it in the
repo's readme).
If you want, you can also just exclude the samples from the release source.
I've seen projects do all three.
But bottom line, you guys want an incubator-edgent-samples repo, right?
John
On Tue, Nov 7, 2017 at 10:25 AM Dale LaBossiere <dm...@gmail.com>
wrote:
> Hmm surprised nothing showed up on @dev. Maybe it was the case that it
> really all/only happened in the wiki page (frequently referenced on dev@)
> where we were tracking all of the issues that came up related to the
> conversion:
> https://cwiki.apache.org/confluence/display/EDGENT/Maven+vs+Gradle <
> https://cwiki.apache.org/confluence/display/EDGENT/Maven+vs+Gradle>
>
> In any case, IMO the “requirement” is that we now need to release a “core”
> source bundle (the Edgent API’s, connectors, etc) AND a “samples” source
> bundle. It was Chris’s opinion that was best addressed by moving the
> samples into their own repo… which I have no problem with.
>
> — Dale
>
> > On Nov 7, 2017, at 10:00 AM, John D. Ament <jo...@apache.org>
> wrote:
> > ...
> > I'm looking through the archives, how was it decided to create an
> > edgent-samples repo? I'm happy to create it, but I see no chatter on
> list
> > indicating its what you guys want.
>
>
Re: Creating a new git repo for the Edgent project
Posted by Dale LaBossiere <dm...@gmail.com>.
Hmm surprised nothing showed up on @dev. Maybe it was the case that it really all/only happened in the wiki page (frequently referenced on dev@) where we were tracking all of the issues that came up related to the conversion: https://cwiki.apache.org/confluence/display/EDGENT/Maven+vs+Gradle <https://cwiki.apache.org/confluence/display/EDGENT/Maven+vs+Gradle>
In any case, IMO the “requirement” is that we now need to release a “core” source bundle (the Edgent API’s, connectors, etc) AND a “samples” source bundle. It was Chris’s opinion that was best addressed by moving the samples into their own repo… which I have no problem with.
— Dale
> On Nov 7, 2017, at 10:00 AM, John D. Ament <jo...@apache.org> wrote:
> ...
> I'm looking through the archives, how was it decided to create an
> edgent-samples repo? I'm happy to create it, but I see no chatter on list
> indicating its what you guys want.
Re: Creating a new git repo for the Edgent project
Posted by "John D. Ament" <jo...@apache.org>.
Hi Chris,
Probably Greg should have said "check with your mentors" rather than check
with me in particular.
I'm looking through the archives, how was it decided to create an
edgent-samples repo? I'm happy to create it, but I see no chatter on list
indicating its what you guys want.
John
On Tue, Nov 7, 2017 at 3:30 AM Christofer Dutz <ch...@c-ware.de>
wrote:
> Hi John,
>
> we have just migrated the entire Edgent project to a Maven build and would
> now like to split out the samples. For that we would require a
> “edgent-samples” git repo. I was told to contact you in order to create
> such a repo.
>
> Could you please do that for us?
>
> Chris
>