JP, if I understand what you're saying, "If we could have one working
location+configuration, be it A' or B' or whatever, I'd be fine with
it,
it'll be better than our current situation", I'm now welcome to delete
jspwiki/trunk/jspwiki-site so we'll just have the single standard
jspwiki/site/trunk that they're used to (indeed they *required* the
roller/site/trunk format when I got Roller on the Apache CMS:
https://issues.apache.org/**jira/browse/INFRA-5631?**
focusedCommentId=13547018&**page=com.atlassian.jira.**
plugin.system.issuetabpanels:**comment-tabpanel#comment-**13547018<https://issues.apache.org/jira/browse/INFRA-5631?focusedCommentId=13547018&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13547018>.)
And then I can close JSPWiki-787, JSPWIKI-5943, and JSPWIKI-6611 and
submit
an Infra JIRA to make the JSPWiki URL (jspwiki.apache.org/jspwiki) just
like the Roller URL (roller.apache.org) on the Apache CMS, i.e., get
rid
of the "jspwiki" subdirectory from the URL. So we'll be back to
having a
single site we can update via normal Apache CMS processes described
on the
Edit Website page of the JSPWiki site.
Further, whatever prettying up you wish to do of the ChangeLog file can
instead be done via CSS and/or us adding our changes in via HTML as
mentioned below, no more autogeneration, OK?
We have to get this issue fixed, and simplifying it to whatever Infra's
accustomed to seems to be the best way to go. (Indeed, in
JSPWIKI-6611,
Daniel has stated our problem is that we're no longer using the
jspwiki/site/trunk location they're expecting:
https://issues.apache.org/*
*jira/browse/INFRA-6611?**focusedCommentId=13729382&**
page=com.atlassian.jira.**plugin.system.issuetabpanels:**
comment-tabpanel#comment-**13729382<https://issues.apache.org/jira/browse/INFRA-6611?focusedCommentId=13729382&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13729382>)
This project has lots of difficulties already, at least let's get
rid of
the crippled website issue.
Regards,
Glen
------------------------------**--------
JP Wrote:
Hi Glen, well not exactly.
Site's src began at location "A" in the SVN tree. We opened INFRA-5943,
and to make things easier to infra, site's src was copied to
location "B",
in order to make the site transition seamless. Graduation came, and
the SVN
was migrated, A location became A' and B became B'. So far so good.
The site was migrated directly from A to B', which seems to be the
cause
of INFRA-6611. As I've understood from INFRA-6611, it should've gone
from A
to A' to B' or from A to B to B', solving 5943 and 6611 one after
another.
Going from A to B' in one step has been the cause of the current
problems
with the website. AFAIK, sticking with the old site location won't
solve
the issue as it still exists right now, it's CMS configuration
problem; I'm
not 100% sure, but seems it has to be recreated (cfr. with INFRA-6492,
duplicate of 6611). If we could have one working
location+configuration, be
it A' or B' or whatever, I'd be fine with it, it'll be better than our
current situation..
Tomorrow is the board meeting, with our report stating this issue,
hopefully it should draw some attention to it br, juan pablo
On 08/20/2013 10:12 AM, Glen Mazza wrote:
JP, it's looking like the website delays are due in part to your
moving
the site folder under our source trunk, and not in the site/cms or
whatever
folder Apache CMS that is accustomed to: https://issues.apache.org/**
jira/browse/INFRA-6611?**focusedCommentId=13729365&**
page=com.atlassian.jira.**plugin.system.issuetabpanels:**
comment-tabpanel#comment-**13729365<https://issues.apache.org/jira/browse/INFRA-6611?focusedCommentId=13729365&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13729365>.
Further, this was done to satisfy INFRA-5943, autogeneration of the
website so the change log would look nicer. I.e., the entire
website is
apparently being crippled just so one page looks perhaps 30% better
via
HTML and CSS. That's leaving aside the problem that 5943 means we
won't
have a staging website to review our changes anymore (all commits go
directly to prod) as well as that every svn code commit presently
reports a
distracting update to the website pages.
I think I have a better solution for us. How about we rename the
ChangeLog to OldChangeLog2 or whatever and move it out of the
root. In its
place, give us a brand-new, empty ChangeLog.html containing a
commented-out
template for us to copy at the top and use everytime we make a
change. I
always blog in pure HTML, so it's absolutely *nothing* for me to
update the
ChangeLog in HTML. Then link to the HTML page on our website
instead, so it
will be nice and formatted as desired and always updated with the
latest
information (no auto-publishing needed). You can put the CSS at
the top of
the ChangeLog or store it at the jspwiki site directory and just
reference
it in. Then we can get the site folder out of the source code
trunk and
back where Apache CMS is coded to expect it, we resume having the
staging/publish site again, our commits just show the code we
changed with
no auto updates to the site, and Infra is happy with us again. How
does
that sound?
If you would prefer a more automated solution than us directly
updating
the HTML file (I'm personally fine with that, though), rather than
roll-our-own I would recommend a JIRA enhancement request (and
patch, if
you wish) to the Apache CMS team for what you have in mind so it gets
implemented there in a standard fashion for all teams.
Regards,
Glen
On 07/31/2013 08:46 PM, Glen Mazza wrote:
OK, good, you're clearly aware of the issue. I'll focus on code
instead...
Glen
On 07/31/2013 06:43 PM, Juan Pablo Santos Rodríguez wrote:
Hi Glen,
I don't mind if INFRA-5943 gets done now or in two months, as
it'll be
an
extra (to publish a nice changelog after every commit), but right
now
I'm
afraid we're unable to update the site, see comments on INFRA-6577
(JSPWiki
TLP: common tasks) and INFRA-6611 (Error updating JSPWiki CMS site).
This
JIRA shouldn't stop manual edits of the website happening though,
i.e.:
when a new release is done
Also, regarding the site SVN location, until INFRA-6492 gets
done, it's
$svn/site/trunk (although we can't push content or move the jspwiki
folder
one level up right now), and afterwards will be
$svn/trunk/jspwiki-site/src/**site/trunk This should be independent
from
INFRA-5943
As soon as we are able to edit the website again, I was hoping to
edit
and
remove all the incubating stuff and publish the site under
jspwiki.a.o
instead of jspwiki.a.o/jspwiki. My idea is to ping infra again by
tomorrow
night to give some space to all these JIRAs (although we've been
over a
week with half site and without a front page :-/)
br,
juan pablo
On Wed, Jul 31, 2013 at 11:24 PM, Glen Mazza <[email protected]>
wrote:
JP, can we hold off on INFRA-5943 (just cancel it for now) so
we can
get
the http://jspwiki.apache.org/ page fully active (no more
linking to
an
HTML index) and I can remove the "(incubating)" references? Just
have
them
do INFRA-6492 and make it clear 5943 is withdrawn. This will entail
deleting one of our two "jspwiki-site" directories--you tell me
which
one--I don't want to be juggling two sources of record for our
website.
I'd like to hold off on 5943 until the jspwiki.org wiki pages
are also
copied over (and also the IT tests are working, if I may get
greedy :)
Whatever its merits (and I've always seen just a link to SVN
for the
changelog good enough), Apache Infra just doesn't have the time to
work on
it, they presently have 115 other "major" issues in JIRA and the
much
more
complex 5943 may be prohibiting them from completing 6492. I don't
think
we can afford a several-week wait, we need to remove the
"incubating"
stuff.
The current fully documented vanilla Apache CMS process (
http://jspwiki.apache.org/****jspwiki/development/edit_****
website.html<http://jspwiki.apache.org/**jspwiki/development/edit_**website.html>
<http://jspwiki.**apache.org/jspwiki/**development/edit_website.html<http://jspwiki.apache.org/jspwiki/development/edit_website.html>
**),
where we commit to SVN, go to the staging site to see if we like
it,
and
then hit the publish button if we do has worked fine, I've never
had a
problem with it and I've done more website updates the past several
months
than anyone here. (Do you know how to use it by the way? The edit
page --
the staging site -- the publish button? I don't know if you
want to
switch
from the current process because you haven't tried out the current
process
yet...)
Regards,
Glen
On 07/22/2013 01:18 PM, Juan Pablo Santos Rodríguez wrote:
Hi Glen,
I tried to do the same edit this morning, same results, I think
it's
related to INFRA-6492 (still open) and the relocation of SVN:
editing
the
site via CMS bookmarklet yields an "Error 500" page, with the
following
message: "Repository has been moved: Repository moved
permanently to '
https://svn.apache.org/repos/****asf/jspwiki/site/trunk/****
content/jspwiki<https://svn.apache.org/repos/**asf/jspwiki/site/trunk/**content/jspwiki>
<https://svn.**apache.org/repos/asf/jspwiki/**
site/trunk/content/jspwiki<https://svn.apache.org/repos/asf/jspwiki/site/trunk/content/jspwiki>>
';
please relocate at
/usr/local/cms/webgui/lib/ASF/****CMS/WC/Commit.pm
line
62".
As per INFRA-6492, it seems the site still needs some tweaking in
order to
be fully usable
Regarding the site folder, once INFRA-6492 gets completed, the
site
folder
should be $svn/trunk/jspwiki-site/src/****site/trunk (I'd
prefer to
delete
$svn/site/trunk once INFRA-6492 gets resolved, just in case)
Regarding the extra jspwiki folder at jspwiki.a.o/jspwiki: the
site
has
been partially transferred, having the same strucure it had
when being
part
of incubator.a.o, and needed to be one level down (the jspwiki
folder), in
order to not "pollute" the main incubator.a.o. Once the site is
relocated
we will be able to push content one level up, effectively
dismissing
the
extra jspwiki we have right now. In that sense I feel INFRA-6572
should be
closed as invalid/duplicated/related to INFRA-6492
Also, when you say you can't commit right now, you are
referring just
to
the site or to all svn (https://svn.apache.org/repos/**
**asf/jspwiki/trunk/<https://svn.apache.org/repos/**asf/jspwiki/trunk/>
<https://**svn.apache.org/repos/asf/**jspwiki/trunk/<https://svn.apache.org/repos/asf/jspwiki/trunk/>
).
The first one should be expected 'til we get solved INFRA-6492,
the
second
one shouldn't happen, right now committer access is given to the
following
apache id's for jspwiki:
juanpablo@minotaur:~$ list_unix_group.pl jspwiki
ajaquith
altheim
brushed
clr
csauer
florianh
gmazza
henning
jalkanen
juanpablo
metskem
rubys
snoopdave
Finally, I'll file the required JIRA for transferring resources
incubator
-> TLP as soon as I get through all the last e-mails this week
br,
juan pablo
On Mon, Jul 22, 2013 at 5:53 PM, Glen Mazza<[email protected]>
wrote:
Hi Juan Pablo, I made an update to jspwiki/jspwiki-site
(namely,
removed
the "(Incubating)" from the title page -- index.html) but the
change
did
not propagate to the website:http://jspwiki.****staging.apache.<
http://**jspwiki.staging.apache <http://jspwiki.staging.apache>.>
**org/jspwiki/<**http://**jspwiki.staging.apache.<http://jspwiki.staging.apache.>
**org/**jspwiki/<http://jspwiki.**staging.apache.org/jspwiki/<http://jspwiki.staging.apache.org/jspwiki/>>
.
I also noticed that the old "site" directory hasn't been
deleted
yet:
http://svn.apache.org/viewvc/******jspwiki/<http://svn.apache.org/viewvc/****jspwiki/>
<http://svn.apache.**org/viewvc/**jspwiki/<http://svn.apache.org/viewvc/**jspwiki/>>
<http://svn.apache.**org/**viewvc/jspwiki/<http://svn.**
apache.org/viewvc/jspwiki/
<http://svn.apache.org/viewvc/jspwiki/>>
.
I assumed as a part of your automated site generation, we
would
still
just
have one folder for our website that would store everything --
either
"site" or "jspwiki/jspwiki-site" -- is that not the case? Can we
consolidate to one folder? Also, could you update the Edit page:
http://jspwiki.staging.apache.******org/jspwiki/development/****
edit_**
website.html<http://jspwiki.****staging.apache.org/jspwiki/**<http://staging.apache.org/jspwiki/**>
development/edit_website.html<**http://jspwiki.staging.apache.**
org/jspwiki/development/edit_**website.html<http://jspwiki.staging.apache.org/jspwiki/development/edit_website.html>>
**for the new website generation process, remove what's no
longer
relevant
and add a blurb explaining the new stuff.
Thanks,
Glen
PS: I can't commit anything myself right now. I put in an Infra
ticket
to
get my (and potentially everyone else's) karma restored:
https://issues.apache.org/******jira/browse/INFRA-6574<https://issues.apache.org/****jira/browse/INFRA-6574>
<https:/**/issues.apache.org/**jira/**browse/INFRA-6574<https://issues.apache.org/**jira/browse/INFRA-6574>>
<https:/**/issues.apache.org/**jira/**browse/INFRA-6574<http://issues.apache.org/jira/**browse/INFRA-6574>
<https**://issues.apache.org/jira/**browse/INFRA-6574<https://issues.apache.org/jira/browse/INFRA-6574>>
