looks good
On Fri, Dec 6, 2019 at 9:28 PM Andy Seaborne wrote:
>
>
> On 06/12/2019 13:38, Marco Neumann wrote:
> > Thanks Adam,
> >
> > the process sounds a bit cumbersome, but in any event the page I have
> > already edited is here
> >
> >
> https://cms.apache.org/jena/wc/edit/anonymous-n3xU7Y/
On 06/12/2019 13:38, Marco Neumann wrote:
Thanks Adam,
the process sounds a bit cumbersome, but in any event the page I have
already edited is here
https://cms.apache.org/jena/wc/edit/anonymous-n3xU7Y/trunk/content/documentation/javadoc/index.mdtext
the idea was to update the bread crumb n
thank you Adam, this will do for now
On Fri, Dec 6, 2019 at 5:05 PM ajs6f wrote:
> Maybe the confusion here is between "committee" (as in PMC) and
> "committers", who are so-called because they have commit rights to the code
> (normally earned by being personally committed to the project). Here
Maybe the confusion here is between "committee" (as in PMC) and "committers",
who are so-called because they have commit rights to the code (normally earned
by being personally committed to the project). Here is some documentation about
what an Apache PMC is and does as opposed to committer-ship
OK I see, I have inferred that from the Apache site [1] where it says that
the Apache Jena Committee is also called PMC .
I have seen a number of changes over the years, even predating the move to
Apache, so yes migrating to a new system might be an option. possibly a
wiki type system. But it's no
No, I didn't mention the PMC at all.
Perhaps we're getting confused here because like other Apache projects, Jena
has both a roster of committers, who have privileges to work on the codebase
and docbase, but also a Project Management Committee or PMC (of which Andy is
now the chair), which is u
in short yes, I would think for documentation purposes and the like a more
relaxed form of participation should be available. So you say currently
only members with role PMC can commit edits to the documentation on the
apache cms? Can roles be dynamically generated here or does each Apache
project
It is not tied into that build process, except for the Javadocs, since Javadocs
are extracted from the codebase. There is no need to build the codebase to
publish the site as a whole.
As for assigning an account to individual users, I'm not quite sure what that
would do. Currently accounts are
if use anonymous as username you should be able to see the changed
structure. basically if you currently access the public site and you select
Spatial Search in the Javadoc drop-down it will lead you to a Not Found
404. I suggest to replace the item with a link to the GeoSPARQL
documentation as out
assign user name and password to individual users? I'd say it doesn't need
to be tied into the build process of the Apache Jena project IIUC
On Fri, Dec 6, 2019 at 3:41 PM ajs6f wrote:
> Did you have suggestions for a different process?
>
> ajs6f
>
> > On Dec 6, 2019, at 8:38 AM, Marco Neumann
Did you have suggestions for a different process?
ajs6f
> On Dec 6, 2019, at 8:38 AM, Marco Neumann wrote:
>
> Thanks Adam,
>
> the process sounds a bit cumbersome, but in any event the page I have
> already edited is here
>
> https://cms.apache.org/jena/wc/edit/anonymous-n3xU7Y/trunk/content
I can't access the link - that can be because it wasn't committed, or it
thinks I'm editing something.
Marco - could you put it on a gist and email the link?
because it is under "javadoc/" it needs special handling as a script
resets tha whole of "javadoc/" as part of the release process.
Thanks Adam,
the process sounds a bit cumbersome, but in any event the page I have
already edited is here
https://cms.apache.org/jena/wc/edit/anonymous-n3xU7Y/trunk/content/documentation/javadoc/index.mdtext
the idea was to update the bread crumb navigation items since currently to
spatial sear
Yes, a committer needs to push the change through to be committed to the
documentation base, and then the site must be published. We always publish for
a release, but we can publish at other times, too, if needed.
I do not recall seeing the actual change come across dev@ (which it normally
woul
14 matches
Mail list logo
