Re: New Repository for Project Archetype

[Robert Munteanu]

Hi Andy,

On Tue, 2018-07-31 at 16:22 -0700, Andreas Schaefer wrote:
> Hi
> 
> I wanted to rekindle this discussion as my project-archetype (in the
> sling-whiteboard git repo) is still open and nothing has happened for
> the past 5 months.
> 
> Someone mentioned that we should start a discussion about which
> archetypes should be part of Sling and maybe merged and which one
> should be retired.
> 
> Headwire’s Peregrine CMS is using this archetype to generate user
> packages but for the IDE Tooling (the last time I checked) content
> can only be edited if it is part of a package rather than a bundle.
> 

We have not set any limitations to the sling whiteboard, so feel free
evolve it as you see fit.

I do believe that we should decide which archetypes we want to support.
Already IMO we have too many and besides the usual arguments related to
documentation and maintenance, it can be confusing for users to see
many, potentially overlapping, archetypes.

So the fewer the better, and if can achieve this with only one
archetype - the one you propose - that's fine. But please start a
dicussion with a concrete proposal on what archetypes to use.

Thanks,

Robert

Re: New Repository for Project Archetype

[Andreas Schaefer]

Hi

I wanted to rekindle this discussion as my project-archetype (in the 
sling-whiteboard git repo) is still open and nothing has happened for the past 
5 months.

Someone mentioned that we should start a discussion about which archetypes 
should be part of Sling and maybe merged and which one should be retired.

Headwire’s Peregrine CMS is using this archetype to generate user packages but 
for the IDE Tooling (the last time I checked) content can only be edited if it 
is part of a package rather than a bundle.

Cheers - Andy Schaefer

> On Jan 22, 2018, at 2:13 AM, Robert Munteanu  wrote:
> 
> On Sun, 2018-01-21 at 14:08 -0800, Andreas Schaefer wrote:
>> Hi
>> 
>> I added the project-archetype to the Sling Whiteboard under a branch
>> feature/sling-7276.
>> 
>> It should deploy just fine on the latest Sling (Sling Starter from
>> GitHub).
>> 
>> Let me know if I should merge this into ‘master’ or if you want to
>> keep the code
>> in that branch for the review.
> 
> I personally don't see a point for having different branches in the
> whiteboard - it's by definition a staging ground, so feel free to merge
> to master.
> 
> Robert

Re: New Repository for Project Archetype

[Robert Munteanu]

On Sun, 2018-01-21 at 14:08 -0800, Andreas Schaefer wrote:
> Hi
> 
> I added the project-archetype to the Sling Whiteboard under a branch
> feature/sling-7276.
> 
> It should deploy just fine on the latest Sling (Sling Starter from
> GitHub).
> 
> Let me know if I should merge this into ‘master’ or if you want to
> keep the code
> in that branch for the review.

I personally don't see a point for having different branches in the
whiteboard - it's by definition a staging ground, so feel free to merge
to master.

Robert

Re: New Repository for Project Archetype

[Andreas Schaefer]

Hi

I added the project-archetype to the Sling Whiteboard under a branch 
feature/sling-7276.

It should deploy just fine on the latest Sling (Sling Starter from GitHub).

Let me know if I should merge this into ‘master’ or if you want to keep the code
in that branch for the review.

Cheers - Andy

> On Jan 21, 2018, at 12:53 PM, Robert Munteanu  wrote:
> 
> On Sat, 2018-01-20 at 20:55 +0100, Konrad Windszus wrote:
>> Hi Andy,
>> please first use the sling-whiteboard Git repo (https://github.com/ap
>> ache/sling-whiteboard ).
>> Then we can start further discussions on code and do the review
>> there.
>> Having it placed in a dedicated repo is really the last step.
>> Thanks,
>> Konrad
> 
> +1
> 
> I would also like to start a discussion on the archetypes we currently
> have. We have too many IMO and should retire some of them and
> consolidate the others.
> 
> Robert

Re: New Repository for Project Archetype

[Robert Munteanu]

On Sat, 2018-01-20 at 20:55 +0100, Konrad Windszus wrote:
> Hi Andy,
> please first use the sling-whiteboard Git repo (https://github.com/ap
> ache/sling-whiteboard ).
> Then we can start further discussions on code and do the review
> there.
> Having it placed in a dedicated repo is really the last step.
> Thanks,
> Konrad

+1

I would also like to start a discussion on the archetypes we currently
have. We have too many IMO and should retire some of them and
consolidate the others.

Robert

Re: New Repository for Project Archetype

[Konrad Windszus]

Hi Andy,
please first use the sling-whiteboard Git repo 
(https://github.com/apache/sling-whiteboard 
). Then we can start further 
discussions on code and do the review there.
Having it placed in a dedicated repo is really the last step.
Thanks,
Konrad

> On 20. Jan 2018, at 20:52, Andreas Schaefer  wrote:
> 
> Hi
> 
> Now that I am a committer I would like to add my Project Archetype:
> Ticket: https://issues.apache.org/jira/browse/SLING-7276
> into Sling but for that I need a new Repository.
> 
> I would suggest ‘project-archetype’ following the naming of the
> other archetypes.
> 
> Thanks - Andy

New Repository for Project Archetype

[Andreas Schaefer]

Hi

Now that I am a committer I would like to add my Project Archetype:
Ticket: https://issues.apache.org/jira/browse/SLING-7276
into Sling but for that I need a new Repository.

I would suggest ‘project-archetype’ following the naming of the
other archetypes.

Thanks - Andy