Re: slingpackager in it's own git repo

On Tue, 2020-04-28 at 07:27 -0700, Henry Saginor wrote: > +1 for /apache/sling-slingpackager Ack, I'll start a vote with this proposed name. Thanks, Robert > > > On Apr 28, 2020, at 5:26 AM, Ruben Reusser wrote: > > > > I think the problem with the naming of the packager has to be > > looked

Re: slingpackager in it's own git repo

+1 for /apache/sling-slingpackager > On Apr 28, 2020, at 5:26 AM, Ruben Reusser wrote: > > I think the problem with the naming of the packager has to be looked at from > the npmjs registry [1] > Ideally we use a similar name for the repo as we would use for publishing to > npm and how we would

Re: slingpackager in it's own git repo

I think the problem with the naming of the packager has to be looked at from the npmjs registry [1] Ideally we use a similar name for the repo as we would use for publishing to npm and how we would like people to use it from the command line. sling-packager is unfortunately already taken and s

Re: slingpackager in it's own git repo

I like js in the name because it lets me know it's not a Java project. Most Sling projects are java and maven. So, repo naming is derived from maven artifact id and "java" does not need to be advertised. I am not sure about cli. I imagine exposing slingpackage operations as API so it can be used by

Re: slingpackager in it's own git repo

On Fri, 2020-04-24 at 11:39 -0700, Henry Saginor wrote: > I am happy to put up the repository name to a vote. Here are the > choices > and reasoning as I see it.. > 1) github.com/apache/sling-slingpackager - short and filterable by > sling- > as project > 2) github.com/apache/sling-js-slingpackager

Re: slingpackager in it's own git repo

I am happy to put up the repository name to a vote. Here are the choices and reasoning as I see it.. 1) github.com/apache/sling-slingpackager - short and filterable by sling- as project 2) github.com/apache/sling-js-slingpackager - the same as 1) but includes js to id it as a js project 3) github.c

Re: slingpackager in it's own git repo

Hi, On Fri, Apr 24, 2020 at 7:58 AM Henry Saginor wrote: > The slingpackage [1] is a nodejs based command line tool for managing content > packages. > Does it make sense to now move it out of whiteboard and into its own > repository? What does everyone think about that? .. +1, taking into acco

Re: slingpackager in it's own git repo

On Fri, 2020-04-24 at 11:04 +0200, Robert Munteanu wrote: > On Thu, 2020-04-23 at 22:58 -0700, Henry Saginor wrote: > > Hi All, > > > > The slingpackage [1] is a nodejs based command line tool for > > managing > > content packages. > > > > Does it make sense to now move it out of whiteboard and

Re: slingpackager in it's own git repo

On Thu, 2020-04-23 at 22:58 -0700, Henry Saginor wrote: > Hi All, > > The slingpackage [1] is a nodejs based command line tool for managing > content packages. > > Does it make sense to now move it out of whiteboard and into its own > repository? What does everyone think about that? +1 What

slingpackager in it's own git repo

Hi All, The slingpackage [1] is a nodejs based command line tool for managing content packages. Does it make sense to now move it out of whiteboard and into its own repository? What does everyone think about that? I also was hoping to discuss how we can publish it to npm. I understand that