Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, 2 Oct 2023 at 14:38, Gary Gregory wrote: > > I agree that we should only advertise active components. I wonder if we > could get the karma to create a GitHub "project" to group all Commons > repositories or if infra has to do that for us. That would alleviate the > need for the table in readme.md pages. This new GH project would still need to be maintained. But at least it would be a single point of failure. Feel free to investigate what would be required, and then we can decide if that is the way to go. It would be better if the same data could somehow be used for both the site generation and other uses such as this. > Gary > > On Mon, Oct 2, 2023, 9:10 AM sebb wrote: > > > On Mon, 2 Oct 2023 at 13:30, Gary Gregory wrote: > > > > > > On Mon, Oct 2, 2023 at 8:04 AM sebb wrote: > > > > > > > > On Mon, 2 Oct 2023 at 11:34, Gary Gregory > > wrote: > > > > > > > > > > My intent was to advertise the breadth of Commons without forcing > > users > > > > > away from GitHub but instead let them jump to another github repo > > directly. > > > > > > > > The problem is that the list gets out of date and needs a lot of > > > > ongoing manual maintenance. > > > > > > I'm not sure I buy that argument. The only change that's happened that > > > I can recall is our recent decision to make [functor] and [ognl] > > > dormant. > > > > I agree that's how I found the issue. > > > > However, the list did not contain OGNL, and it contained Signing, > > which was retired ages ago. > > > > So it was already out of date (and see below). > > > > > If that's how you want to advertise Commons to the wider > > > GitHub world, then go for it ;-) > > > > Do we really want to advertise dormant/retired/sandbox/internal > > projects in this way? > > > > For example, > > https://github.com/apache/commons-lang#apache-commons-components > > currently includes Signing, which has a link to a non-existent > > website. > > > > I've also just noticed that the template links to Graph which is in the > > Sandbox. > > > > There are also links to internal components such as the Build Plugin > > and Commons Parent. > > As well as Testing - status unknown (and no website AFAICT) > > > > > Gary > > > > > > > > > > > > Gary > > > > > > > > > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > > > > > > > > > The Build Plugin currently includes a list of components in the > > README > > > > > > template. > > > > > > > > > > > > This duplicates information provided elsewhere, and gets out of > > date. > > > > > > > > > > > > Since this info is in every GH repo, any changes also need to be > > > > > > applied to every one of them, to ensure they are up to date. > > > > > > > > > > > > This is an unnecessary maintenance burden. > > > > > > > > > > > > I think this local list should be dropped, and replaced with a > > link to > > > > > > the main website. > > > > > > > > > > > > Sebb > > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [BUILD-PLUGIN] Drop component list from README template?
I agree that we should only advertise active components. I wonder if we could get the karma to create a GitHub "project" to group all Commons repositories or if infra has to do that for us. That would alleviate the need for the table in readme.md pages. Gary On Mon, Oct 2, 2023, 9:10 AM sebb wrote: > On Mon, 2 Oct 2023 at 13:30, Gary Gregory wrote: > > > > On Mon, Oct 2, 2023 at 8:04 AM sebb wrote: > > > > > > On Mon, 2 Oct 2023 at 11:34, Gary Gregory > wrote: > > > > > > > > My intent was to advertise the breadth of Commons without forcing > users > > > > away from GitHub but instead let them jump to another github repo > directly. > > > > > > The problem is that the list gets out of date and needs a lot of > > > ongoing manual maintenance. > > > > I'm not sure I buy that argument. The only change that's happened that > > I can recall is our recent decision to make [functor] and [ognl] > > dormant. > > I agree that's how I found the issue. > > However, the list did not contain OGNL, and it contained Signing, > which was retired ages ago. > > So it was already out of date (and see below). > > > If that's how you want to advertise Commons to the wider > > GitHub world, then go for it ;-) > > Do we really want to advertise dormant/retired/sandbox/internal > projects in this way? > > For example, > https://github.com/apache/commons-lang#apache-commons-components > currently includes Signing, which has a link to a non-existent > website. > > I've also just noticed that the template links to Graph which is in the > Sandbox. > > There are also links to internal components such as the Build Plugin > and Commons Parent. > As well as Testing - status unknown (and no website AFAICT) > > > Gary > > > > > > > > > Gary > > > > > > > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > > > > > > > The Build Plugin currently includes a list of components in the > README > > > > > template. > > > > > > > > > > This duplicates information provided elsewhere, and gets out of > date. > > > > > > > > > > Since this info is in every GH repo, any changes also need to be > > > > > applied to every one of them, to ensure they are up to date. > > > > > > > > > > This is an unnecessary maintenance burden. > > > > > > > > > > I think this local list should be dropped, and replaced with a > link to > > > > > the main website. > > > > > > > > > > Sebb > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, 2 Oct 2023 at 13:30, Gary Gregory wrote: > > On Mon, Oct 2, 2023 at 8:04 AM sebb wrote: > > > > On Mon, 2 Oct 2023 at 11:34, Gary Gregory wrote: > > > > > > My intent was to advertise the breadth of Commons without forcing users > > > away from GitHub but instead let them jump to another github repo > > > directly. > > > > The problem is that the list gets out of date and needs a lot of > > ongoing manual maintenance. > > I'm not sure I buy that argument. The only change that's happened that > I can recall is our recent decision to make [functor] and [ognl] > dormant. I agree that's how I found the issue. However, the list did not contain OGNL, and it contained Signing, which was retired ages ago. So it was already out of date (and see below). > If that's how you want to advertise Commons to the wider > GitHub world, then go for it ;-) Do we really want to advertise dormant/retired/sandbox/internal projects in this way? For example, https://github.com/apache/commons-lang#apache-commons-components currently includes Signing, which has a link to a non-existent website. I've also just noticed that the template links to Graph which is in the Sandbox. There are also links to internal components such as the Build Plugin and Commons Parent. As well as Testing - status unknown (and no website AFAICT) > Gary > > > > > > Gary > > > > > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > > > > > The Build Plugin currently includes a list of components in the README > > > > template. > > > > > > > > This duplicates information provided elsewhere, and gets out of date. > > > > > > > > Since this info is in every GH repo, any changes also need to be > > > > applied to every one of them, to ensure they are up to date. > > > > > > > > This is an unnecessary maintenance burden. > > > > > > > > I think this local list should be dropped, and replaced with a link to > > > > the main website. > > > > > > > > Sebb > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, Oct 2, 2023 at 8:04 AM sebb wrote: > > On Mon, 2 Oct 2023 at 11:34, Gary Gregory wrote: > > > > My intent was to advertise the breadth of Commons without forcing users > > away from GitHub but instead let them jump to another github repo directly. > > The problem is that the list gets out of date and needs a lot of > ongoing manual maintenance. I'm not sure I buy that argument. The only change that's happened that I can recall is our recent decision to make [functor] and [ognl] dormant. If that's how you want to advertise Commons to the wider GitHub world, then go for it ;-) Gary > > > Gary > > > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > > > The Build Plugin currently includes a list of components in the README > > > template. > > > > > > This duplicates information provided elsewhere, and gets out of date. > > > > > > Since this info is in every GH repo, any changes also need to be > > > applied to every one of them, to ensure they are up to date. > > > > > > This is an unnecessary maintenance burden. > > > > > > I think this local list should be dropped, and replaced with a link to > > > the main website. > > > > > > Sebb > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, 2 Oct 2023 at 11:34, Gary Gregory wrote: > > My intent was to advertise the breadth of Commons without forcing users > away from GitHub but instead let them jump to another github repo directly. The problem is that the list gets out of date and needs a lot of ongoing manual maintenance. > Gary > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > The Build Plugin currently includes a list of components in the README > > template. > > > > This duplicates information provided elsewhere, and gets out of date. > > > > Since this info is in every GH repo, any changes also need to be > > applied to every one of them, to ensure they are up to date. > > > > This is an unnecessary maintenance burden. > > > > I think this local list should be dropped, and replaced with a link to > > the main website. > > > > Sebb > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [BUILD-PLUGIN] Drop component list from README template?
My intent was to advertise the breadth of Commons without forcing users away from GitHub but instead let them jump to another github repo directly. Gary On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > The Build Plugin currently includes a list of components in the README > template. > > This duplicates information provided elsewhere, and gets out of date. > > Since this info is in every GH repo, any changes also need to be > applied to every one of them, to ensure they are up to date. > > This is an unnecessary maintenance burden. > > I think this local list should be dropped, and replaced with a link to > the main website. > > Sebb > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, 2 Oct 2023 at 10:05, sebb wrote: > > The Build Plugin currently includes a list of components in the README > template. > > This duplicates information provided elsewhere, and gets out of date. > > Since this info is in every GH repo, any changes also need to be > applied to every one of them, to ensure they are up to date. > > This is an unnecessary maintenance burden. > > I think this local list should be dropped, and replaced with a link to > the main website. +1 Alex - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[BUILD-PLUGIN] Drop component list from README template?
The Build Plugin currently includes a list of components in the README template. This duplicates information provided elsewhere, and gets out of date. Since this info is in every GH repo, any changes also need to be applied to every one of them, to ensure they are up to date. This is an unnecessary maintenance burden. I think this local list should be dropped, and replaced with a link to the main website. Sebb - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
