You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2022/09/08 11:29:36 UTC
Suggestions for changes to code file layout
1/ We have a number of retired modules:
apache-jena-osgi
jena-csv
jena-elephas
jena-fuseki1
jena-maven-tools
jena-sdb
jena-spatial
jena-text-es
Each has a README that explains how to retrieve the code from git.
That's 8 of total of 29 top level modules.
Proposal: move these in an "archive/" directory.
2/ Move jena-tdb2 up to the top level from inside jena-db/ to make it
more findable. (After PR #1514 which makes
3/ It is tempting to change jena-tdb/ directory to jena-tdb1/ (maven
artifact not renamed) as well for clarity.
Andy
Re: Suggestions for changes to code file layout
Posted by aj...@apache.org.
+1 to that note, and +1 to git rm.
Adam
On Sun, Sep 11, 2022, 7:23 PM Bruno Kinoshita <br...@gmail.com>
wrote:
> Looks good to me! +1
>
> On Mon, 12 Sept 2022 at 09:18, Andy Seaborne <an...@apache.org> wrote:
>
> > Like this?
> >
> > https://github.com/afs/jena/blob/reorg/archived-modules.md
> >
> > On 10/09/2022 13:30, Andy Seaborne wrote:
> > >
> > >
> > > On 09/09/2022 00:17, Bruno Kinoshita wrote:
> > >> Sounds good.
> > >>
> > >> Is there a reason for not removing the directories, instead of moving
> to
> > >> archive? If we have a note in the README telling users who came
> > >> looking for
> > >> these modules that they are now in the archive folder; we could
> instead
> > >> tell them to use git? Maybe point to the last commit or tag, use a
> > GitHub
> > >> link, etc?
> > >
> > > No specific reason except it's just a "git mv".
> > >
> > > We could have a single file that takes the information already in the
> > > separate README files.
> > >
> > > They have date of retirement and git commit for the last code before
> git
> > > rm. Also text in most of them:
> > > """
> > > Retired modules can be incorporated back into Jena releases if there is
> > > sufficient activity to maintain the code over the long term.
> > > """
> > >
> > > Andy
> > >
> > >>
> > >> Thanks
> > >> Bruno
> > >>
> > >> On Thu, 8 Sept 2022 at 23:29, Andy Seaborne <an...@apache.org> wrote:
> > >>
> > >>> 1/ We have a number of retired modules:
> > >>>
> > >>> apache-jena-osgi
> > >>> jena-csv
> > >>> jena-elephas
> > >>> jena-fuseki1
> > >>> jena-maven-tools
> > >>> jena-sdb
> > >>> jena-spatial
> > >>> jena-text-es
> > >>>
> > >>> Each has a README that explains how to retrieve the code from git.
> > >>>
> > >>> That's 8 of total of 29 top level modules.
> > >>>
> > >>> Proposal: move these in an "archive/" directory.
> > >>>
> > >>>
> > >>> 2/ Move jena-tdb2 up to the top level from inside jena-db/ to make it
> > >>> more findable. (After PR #1514 which makes
> > >>>
> > >>>
> > >>> 3/ It is tempting to change jena-tdb/ directory to jena-tdb1/ (maven
> > >>> artifact not renamed) as well for clarity.
> > >>>
> > >>>
> > >>> Andy
> > >>>
> > >>
> >
>
Re: Suggestions for changes to code file layout
Posted by Bruno Kinoshita <br...@gmail.com>.
Looks good to me! +1
On Mon, 12 Sept 2022 at 09:18, Andy Seaborne <an...@apache.org> wrote:
> Like this?
>
> https://github.com/afs/jena/blob/reorg/archived-modules.md
>
> On 10/09/2022 13:30, Andy Seaborne wrote:
> >
> >
> > On 09/09/2022 00:17, Bruno Kinoshita wrote:
> >> Sounds good.
> >>
> >> Is there a reason for not removing the directories, instead of moving to
> >> archive? If we have a note in the README telling users who came
> >> looking for
> >> these modules that they are now in the archive folder; we could instead
> >> tell them to use git? Maybe point to the last commit or tag, use a
> GitHub
> >> link, etc?
> >
> > No specific reason except it's just a "git mv".
> >
> > We could have a single file that takes the information already in the
> > separate README files.
> >
> > They have date of retirement and git commit for the last code before git
> > rm. Also text in most of them:
> > """
> > Retired modules can be incorporated back into Jena releases if there is
> > sufficient activity to maintain the code over the long term.
> > """
> >
> > Andy
> >
> >>
> >> Thanks
> >> Bruno
> >>
> >> On Thu, 8 Sept 2022 at 23:29, Andy Seaborne <an...@apache.org> wrote:
> >>
> >>> 1/ We have a number of retired modules:
> >>>
> >>> apache-jena-osgi
> >>> jena-csv
> >>> jena-elephas
> >>> jena-fuseki1
> >>> jena-maven-tools
> >>> jena-sdb
> >>> jena-spatial
> >>> jena-text-es
> >>>
> >>> Each has a README that explains how to retrieve the code from git.
> >>>
> >>> That's 8 of total of 29 top level modules.
> >>>
> >>> Proposal: move these in an "archive/" directory.
> >>>
> >>>
> >>> 2/ Move jena-tdb2 up to the top level from inside jena-db/ to make it
> >>> more findable. (After PR #1514 which makes
> >>>
> >>>
> >>> 3/ It is tempting to change jena-tdb/ directory to jena-tdb1/ (maven
> >>> artifact not renamed) as well for clarity.
> >>>
> >>>
> >>> Andy
> >>>
> >>
>
Re: Suggestions for changes to code file layout
Posted by Andy Seaborne <an...@apache.org>.
Like this?
https://github.com/afs/jena/blob/reorg/archived-modules.md
On 10/09/2022 13:30, Andy Seaborne wrote:
>
>
> On 09/09/2022 00:17, Bruno Kinoshita wrote:
>> Sounds good.
>>
>> Is there a reason for not removing the directories, instead of moving to
>> archive? If we have a note in the README telling users who came
>> looking for
>> these modules that they are now in the archive folder; we could instead
>> tell them to use git? Maybe point to the last commit or tag, use a GitHub
>> link, etc?
>
> No specific reason except it's just a "git mv".
>
> We could have a single file that takes the information already in the
> separate README files.
>
> They have date of retirement and git commit for the last code before git
> rm. Also text in most of them:
> """
> Retired modules can be incorporated back into Jena releases if there is
> sufficient activity to maintain the code over the long term.
> """
>
> Andy
>
>>
>> Thanks
>> Bruno
>>
>> On Thu, 8 Sept 2022 at 23:29, Andy Seaborne <an...@apache.org> wrote:
>>
>>> 1/ We have a number of retired modules:
>>>
>>> apache-jena-osgi
>>> jena-csv
>>> jena-elephas
>>> jena-fuseki1
>>> jena-maven-tools
>>> jena-sdb
>>> jena-spatial
>>> jena-text-es
>>>
>>> Each has a README that explains how to retrieve the code from git.
>>>
>>> That's 8 of total of 29 top level modules.
>>>
>>> Proposal: move these in an "archive/" directory.
>>>
>>>
>>> 2/ Move jena-tdb2 up to the top level from inside jena-db/ to make it
>>> more findable. (After PR #1514 which makes
>>>
>>>
>>> 3/ It is tempting to change jena-tdb/ directory to jena-tdb1/ (maven
>>> artifact not renamed) as well for clarity.
>>>
>>>
>>> Andy
>>>
>>
Re: Suggestions for changes to code file layout
Posted by Andy Seaborne <an...@apache.org>.
On 09/09/2022 00:17, Bruno Kinoshita wrote:
> Sounds good.
>
> Is there a reason for not removing the directories, instead of moving to
> archive? If we have a note in the README telling users who came looking for
> these modules that they are now in the archive folder; we could instead
> tell them to use git? Maybe point to the last commit or tag, use a GitHub
> link, etc?
No specific reason except it's just a "git mv".
We could have a single file that takes the information already in the
separate README files.
They have date of retirement and git commit for the last code before git
rm. Also text in most of them:
"""
Retired modules can be incorporated back into Jena releases if there is
sufficient activity to maintain the code over the long term.
"""
Andy
>
> Thanks
> Bruno
>
> On Thu, 8 Sept 2022 at 23:29, Andy Seaborne <an...@apache.org> wrote:
>
>> 1/ We have a number of retired modules:
>>
>> apache-jena-osgi
>> jena-csv
>> jena-elephas
>> jena-fuseki1
>> jena-maven-tools
>> jena-sdb
>> jena-spatial
>> jena-text-es
>>
>> Each has a README that explains how to retrieve the code from git.
>>
>> That's 8 of total of 29 top level modules.
>>
>> Proposal: move these in an "archive/" directory.
>>
>>
>> 2/ Move jena-tdb2 up to the top level from inside jena-db/ to make it
>> more findable. (After PR #1514 which makes
>>
>>
>> 3/ It is tempting to change jena-tdb/ directory to jena-tdb1/ (maven
>> artifact not renamed) as well for clarity.
>>
>>
>> Andy
>>
>
Re: Suggestions for changes to code file layout
Posted by Bruno Kinoshita <ki...@apache.org>.
Sounds good.
Is there a reason for not removing the directories, instead of moving to
archive? If we have a note in the README telling users who came looking for
these modules that they are now in the archive folder; we could instead
tell them to use git? Maybe point to the last commit or tag, use a GitHub
link, etc?
Thanks
Bruno
On Thu, 8 Sept 2022 at 23:29, Andy Seaborne <an...@apache.org> wrote:
> 1/ We have a number of retired modules:
>
> apache-jena-osgi
> jena-csv
> jena-elephas
> jena-fuseki1
> jena-maven-tools
> jena-sdb
> jena-spatial
> jena-text-es
>
> Each has a README that explains how to retrieve the code from git.
>
> That's 8 of total of 29 top level modules.
>
> Proposal: move these in an "archive/" directory.
>
>
> 2/ Move jena-tdb2 up to the top level from inside jena-db/ to make it
> more findable. (After PR #1514 which makes
>
>
> 3/ It is tempting to change jena-tdb/ directory to jena-tdb1/ (maven
> artifact not renamed) as well for clarity.
>
>
> Andy
>
Re: Suggestions for changes to code file layout
Posted by "rvesse@dotnetrdf.org" <rv...@dotnetrdf.org>.
+1 to all three suggestions
For 1 maybe also a README inside archive that explains the purpose of that folder
Rob
From: Andy Seaborne <an...@apache.org>
Date: Thursday, 8 September 2022 at 12:30
To: dev@jena.apache.org <de...@jena.apache.org>
Subject: Suggestions for changes to code file layout
1/ We have a number of retired modules:
apache-jena-osgi
jena-csv
jena-elephas
jena-fuseki1
jena-maven-tools
jena-sdb
jena-spatial
jena-text-es
Each has a README that explains how to retrieve the code from git.
That's 8 of total of 29 top level modules.
Proposal: move these in an "archive/" directory.
2/ Move jena-tdb2 up to the top level from inside jena-db/ to make it
more findable. (After PR #1514 which makes
3/ It is tempting to change jena-tdb/ directory to jena-tdb1/ (maven
artifact not renamed) as well for clarity.
Andy