You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Sahlberg <da...@gmail.com> on 2021/07/02 22:05:49 UTC

Re: Web site link cleanup

Den sön 27 juni 2021 kl 23:36 skrev Daniel Shahaf <d....@daniel.shahaf.name>:

> Daniel Sahlberg wrote on Sun, Jun 27, 2021 at 23:14:20 +0200:
> > Den sön 27 juni 2021 kl 20:34 skrev Daniel Shahaf <
> d.s@daniel.shahaf.name>:
> > Daniel Sahlberg wrote on Sat, 26 Jun 2021 21:12 +00:00:
> > >
> https://www.elegosoft.com/en_US/page/nachlese-subversion-hackathon-berlin-2013
> ,
> > > however that page is only in german now. I'm considering linking to
> > > archive.org, however there are some recorded talks and interviews
> that I
> > > can't find anymore. Does anyone have the original
> > >
> > > Do you mean these? —
> > >
>
> [One level of >-quoting is missing here.]
>
> > >
> SVN_Hackathon_Berlin_2013-01-What_is_New_in_Subversion_1-8_with_Stefan_Sperling.mp4
> > > SVN_Hackathon_Berlin_2013-02-Interview_with_C_Michael_Pilato.mp4
> > >
> > >
> SVN_Hackathon_Berlin_2013-03-Automatic_Mergin_in_Subversion_1-8_with_Julian_Foad.mp4
> > >
> > >
> SVN_Hackathon_Berlin_2013-04-On_the_Way_to_Fast_and_Scalable_Repositories_with_Stefan_Fuhrmann.mp4
> > > SVN_Hackathon_Berlin_2013-05-Interview_with_Johan_Corveleyn.mp4
> > > SVN_Hackathon_Berlin_2013-06-Interview_with_Bert_Huijben.mp4
> > >
> > >
> SVN_Hackathon_Berlin_2013-07-Why_Git_Merges_Better_than_Subversion_with_Neels_J_Hofmeyr.mp4
> > > SVN_Hackathon_Berlin_2013-08-Interview_with_Ben_Reser.mp4
> > > SVN_Hackathon_Berlin_2013-09-Interview_with_Branko_Cibej.mp4
> > >
> > > I have a copy of them.
> > >
> >
> > These are the ones, yes. I see four different options with this link:
>
> Note there are *two* links to that page: one in news.html, one in HACKING.
>

Thanks for the heads-up. These didn't turn up in my grep-ing since I was
only looking for http://.

There are additiona links for the years 2010, 2011, 2012, 2014, 2015 and
2016 (in http://subversion.apache.org/docs/community-guide/general.html)
which I cannot find at all in the current elegosoft.com site.

However "... meets in Berlin for a Hackathon once a year: 2016, 2015, ..."
doesn't seem very current. For this reason I'd suggest to remove the
complete paragraph from HACKING. Other option to rephrase "in the past ...
met in Berlin" and link to archive.org.


> > - Modify the link to point to elego's current site. Pro: Least work, also
> > linking to a current site. Con: In german, only and doesn't contain the
> > links to the interviews.
>
> How do you get the German version?  Here I get only a 404.
>

Oh, sorry. Missed one step: Remove _US from the redirection target, which
in turn redirects to:

https://www.elegosoft.com/en/nachlese-subversion-hackathon-berlin-2013/

> - Modify the link to point to elego's old site via archive.org. Pro: "As
> it
> > was supposed to be" Con: That page (
> >
> https://web.archive.org/web/20171206002300/https://www.elegosoft.com/en_US/page/nachlese-subversion-hackathon-berlin-2013
> )
> > contains links to the interviews, but those links are 404.
> > - Keep the link, but mark it as obsolete. Pro: No re-writing of history.
> > Con: We loose some part of history.
> > - Copy the contents from archive.org and host it including the
> interviews
> > on the site or in WIKI. Pro: Preserve history. Con: Copyright issue needs
> > to be resolved with elego (and whoever took the photos).
>
> Fifth option:
>
> - Link to elego's page in archive.org, and mirror the interviews (with
>   permission, if one is needed)
>

I thought about this but I couldn't invent a way to inject the interviews
within archive.org and thus it didn't provide a good user expericen, which
is why I didn't list this as an option.


> Also, regardless of what we do, it's probably a good idea that someone
> other than me should have a copy of the interviews, if nothing else then
> for future archaeologists.
>
> >
> > > > and could we add them to our own site?
> > >
> > > If elego doesn't mind, I guess?
> > >
> >
> > I should rephrase: Do we want to? Are there still relevant information in
> > these interviews?
> >
>
> I guess they have value, if only historical.
>
> > > > * There are a lot of links in /docs/ concerning older versions.
> Should
> > > > we keep them frozen as a historic document or try to update them? For
> > > > future versions, I will try to fix the obvious in the code (but
> that's
> > > > another project).
> > >
> > > Not sure what you have in mind here.  Example?
> > >
> >
> > Links to java.sun.com in the javahl docs. This is probably from
> docstrings
> > in the source.
> > Links to www.doxygen.org in the api docs. These are "generated by".
> >
> > I'm leaning towards leaving old docs as-is (especially the "generated
> by"),
> > but change the docstrings in the source for a future release.
> >
>
> Sure.  And FWIW, there's nothing stopping us from updating the links in
> the HEAD revision of old minor branches, including unsupported ones.
> That doesn't even require STATUS voting [1].
>
> [1]
> https://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization-backportable-changes


Alright. And it might be possible to only update this within the website
and not changing the old tags/regenerating the docs from source so no
voting required at all. However since it is quite a bit of work I'll only
do it if someone say "we MUST".

I'll try to find some time to update the docstrings in /trunk within the
next few weeks.

Kind regards
Daniel Sahlberg

Re: Web site link cleanup

Posted by Daniel Sahlberg <da...@gmail.com>.
Den tis 6 juli 2021 kl 03:39 skrev Daniel Shahaf <d....@daniel.shahaf.name>:

> Daniel Sahlberg wrote on Sat, Jul 03, 2021 at 00:05:49 +0200:
> > Den sön 27 juni 2021 kl 23:36 skrev Daniel Shahaf:
> > > Daniel Sahlberg wrote on Sun, Jun 27, 2021 at 23:14:20 +0200:
> > > > Den sön 27 juni 2021 kl 20:34 skrev Daniel Shahaf:
> > > > Daniel Sahlberg wrote on Sat, 26 Jun 2021 21:12 +00:00:
> > There are additiona links for the years 2010, 2011, 2012, 2014, 2015 and
> > 2016 (in http://subversion.apache.org/docs/community-guide/general.html)
> > which I cannot find at all in the current elegosoft.com site.
> >
> > However "... meets in Berlin for a Hackathon once a year: 2016, 2015,
> ..."
> > doesn't seem very current. For this reason I'd suggest to remove the
> > complete paragraph from HACKING. Other option to rephrase "in the past
> ...
> > met in Berlin" and link to archive.org.
> >
>
> I prefer not to remove the paragraph; it's a useful historical perspective.
>
> > > - Modify the link to point to elego's old site via archive.org. Pro:
> "As
> > > it
> > > > was supposed to be" Con: That page (
> > > >
> > >
> https://web.archive.org/web/20171206002300/https://www.elegosoft.com/en_US/page/nachlese-subversion-hackathon-berlin-2013
> > > )
> > > > contains links to the interviews, but those links are 404.
> > > > - Keep the link, but mark it as obsolete. Pro: No re-writing of
> history.
> > > > Con: We loose some part of history.
> > > > - Copy the contents from archive.org and host it including the
> > > interviews
> > > > on the site or in WIKI. Pro: Preserve history. Con: Copyright issue
> needs
> > > > to be resolved with elego (and whoever took the photos).
> > >
> > > Fifth option:
> > >
> > > - Link to elego's page in archive.org, and mirror the interviews (with
> > >   permission, if one is needed)
> > >
> >
> > I thought about this but I couldn't invent a way to inject the interviews
> > within archive.org and thus it didn't provide a good user expericen,
> which
> > is why I didn't list this as an option.
> >
>
> It's not the best UX, agreed, but it preserves all available content,
> and in English.  Let's see what others think.
>

Thanks for your feedback. I've not heard from anyone else so for now I've
updated the above links to point to archive.org in r1891737 and rephrased
slightly.

Kind regards,
Daniel

Re: Web site link cleanup

Posted by Daniel Sahlberg <da...@gmail.com>.
Thanks for your feedback! I've left the e-mail in my inbox and intend to
look at the elego links again later on (hoping for input from others on how
to change them, but otherwise I'll try to make it work).

Den tis 6 juli 2021 kl 03:39 skrev Daniel Shahaf <d....@daniel.shahaf.name>:

> Daniel Sahlberg wrote on Sat, Jul 03, 2021 at 00:05:49 +0200:
> > I'll try to find some time to update the docstrings in /trunk within the
> > next few weeks.
>
> Thanks, Daniel.
>

For anyone following this thread but not reading commits@, I have committed
a series of patches, changing links in the source code: r1891236, r1891253,
r1891287.

Kind regards,
Daniel Sahlberg

Re: Web site link cleanup

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Daniel Sahlberg wrote on Sat, Jul 03, 2021 at 00:05:49 +0200:
> Den sön 27 juni 2021 kl 23:36 skrev Daniel Shahaf:
> > Daniel Sahlberg wrote on Sun, Jun 27, 2021 at 23:14:20 +0200:
> > > Den sön 27 juni 2021 kl 20:34 skrev Daniel Shahaf:
> > > Daniel Sahlberg wrote on Sat, 26 Jun 2021 21:12 +00:00:
> There are additiona links for the years 2010, 2011, 2012, 2014, 2015 and
> 2016 (in http://subversion.apache.org/docs/community-guide/general.html)
> which I cannot find at all in the current elegosoft.com site.
> 
> However "... meets in Berlin for a Hackathon once a year: 2016, 2015, ..."
> doesn't seem very current. For this reason I'd suggest to remove the
> complete paragraph from HACKING. Other option to rephrase "in the past ...
> met in Berlin" and link to archive.org.
> 

I prefer not to remove the paragraph; it's a useful historical perspective.

> > - Modify the link to point to elego's old site via archive.org. Pro: "As
> > it
> > > was supposed to be" Con: That page (
> > >
> > https://web.archive.org/web/20171206002300/https://www.elegosoft.com/en_US/page/nachlese-subversion-hackathon-berlin-2013
> > )
> > > contains links to the interviews, but those links are 404.
> > > - Keep the link, but mark it as obsolete. Pro: No re-writing of history.
> > > Con: We loose some part of history.
> > > - Copy the contents from archive.org and host it including the
> > interviews
> > > on the site or in WIKI. Pro: Preserve history. Con: Copyright issue needs
> > > to be resolved with elego (and whoever took the photos).
> >
> > Fifth option:
> >
> > - Link to elego's page in archive.org, and mirror the interviews (with
> >   permission, if one is needed)
> >
> 
> I thought about this but I couldn't invent a way to inject the interviews
> within archive.org and thus it didn't provide a good user expericen, which
> is why I didn't list this as an option.
> 

It's not the best UX, agreed, but it preserves all available content,
and in English.  Let's see what others think.

> > > > > * There are a lot of links in /docs/ concerning older versions.
> > Should
> > > > > we keep them frozen as a historic document or try to update them? For
> > > > > future versions, I will try to fix the obvious in the code (but
> > that's
> > > > > another project).
> > > >
> > > > Not sure what you have in mind here.  Example?
> > > >
> > >
> > > Links to java.sun.com in the javahl docs. This is probably from
> > docstrings
> > > in the source.
> > > Links to www.doxygen.org in the api docs. These are "generated by".
> > >
> > > I'm leaning towards leaving old docs as-is (especially the "generated
> > by"),
> > > but change the docstrings in the source for a future release.
> > >
> >
> > Sure.  And FWIW, there's nothing stopping us from updating the links in
> > the HEAD revision of old minor branches, including unsupported ones.
> > That doesn't even require STATUS voting [1].
> >
> > [1]
> > https://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization-backportable-changes
> 
> 
> Alright. And it might be possible to only update this within the website
> and not changing the old tags/regenerating the docs from source so no
> voting required at all. However since it is quite a bit of work I'll only
> do it if someone say "we MUST".
> 

Sure.  And to be clear, we shouldn't edit old tags for this.  If we need
to change a tag, we can create a branch off it, or make the change in
the 1.A.x branch [assuming it has no other relevant changes].

> I'll try to find some time to update the docstrings in /trunk within the
> next few weeks.

Thanks, Daniel.

Daniel