Re: Data Migration

[Christian Froehler]

Hi,

I have used Jürgen's "migratePlugin" to migrate JSPWiki pages from 
JDBCProvider (mysql) to plain text files, and have enhanced it to handle 
also attachments. The history of page edits was transfered, too, but the 
timestamps of the edits got lost -- older versions of the pages now have 
all the same date.


Should be possible the other way round, from plain text to JDBCProvider.

I hope to find the sources of the "attachment" enhancement, and will 
publish them on github.


Christian

Am 28.11.17 um 18:28 schrieb Jürgen Weber:

As for migrating, I once hacked a simple Plugin to migrate to a different
provider, it might be useful as copy template..

https://github.com/weberjn/migratePlugin

Re: [VOTE] Move to github as the primary repo

[Rick Brockman]

+1 

thanks 

-rick 

On 2017-11-28 18:41, Dirk Frederickx wrote:

> +1
> 
> kr
> dirk
> 
> On Wed, Nov 29, 2017 at 12:33 AM, Juan Pablo Santos Rodríguez <
> juanpablo.san...@gmail.com> wrote:
> 
> and my +1.
> 
> br,
> juan pablo
> 
> On Wed, Nov 29, 2017 at 12:33 AM, Juan Pablo Santos Rodríguez <
> juanpablo.san...@gmail.com> wrote:
> 
> Hi all,
> 
> As noted else-thread, we're currently using ASF's git repo as the
> canonical repo with a read-only copy at github, but infra offers from a
> while back now the opposite possibility: work with github repo, which sends 
> the commits automatically to the ASF's repo, which gets then read-only. It 
> woukd treat Github as the canonical source (a copy on ASF's repo would
> still be made), which allows the PRs and issues to be a bit more convenient 
> (there are still some things not supported due to the Github's coarse
> permission structure). It would be required all committers to use Github's 
> 2FA [https://help.github.com/articles/providing-your-2fa-
> authentication-code/]
> 
> This is the formal VOTE required by infra to set github as the primary
> repo for Apache JSPWiki, and as such subject to the usual voting
> guidelines: it will be open for at least 72 hours, everybody is encouraged to 
> vote, although only PMC ones are binding.
> 
> [+1] yes, move to github as the primary repo
> [0] don't mind
> [-1] we are fine as it is now
> 
> best regards,
> juan pablo

-- 

-

_RICK BROCKMAN_ 

_28 LANCASTER ST._ 

_CHERRY VALLEY, NY 13320_ 

_607 434-4746_

jspwiki topic on github for your custom jspwiki extension

[Juan Pablo Santos Rodríguez]

Hi,

a little off-topic, but I've noticed earlier this week that github allows,
from some months back, to add topics (like in tags, or labels) to your
repos [1], so they can become more easily discoverable. So if you're
hosting a plugin, filter or whatever other extension on your github repo,
please consider adding a jspwiki topic to it :-)

(as it's really late here I'll put a note with this on the appropiate pages
at jspwiki.a.o tomorrow, unless someone beats me to it)


cheers,
juan pablo

[1]: https://github.com/blog/2309-introducing-topics

[VOTE] Move to github as the primary repo

[Juan Pablo Santos Rodríguez]

Hi all,

As noted else-thread, we're currently using ASF's git repo as the canonical
repo with a read-only copy at github, but infra offers from a while back
now the opposite possibility: work with github repo, which sends the
commits automatically to the ASF's repo, which gets then read-only. It
woukd treat Github as the canonical source (a copy on ASF's repo would
still be made), which allows the PRs and issues to be a bit more convenient
(there are still some things not supported due to the Github's coarse
permission structure). It would be required all committers to use Github's
2FA [
https://help.github.com/articles/providing-your-2fa-authentication-code/]

This is the formal VOTE required by infra to set github as the primary repo
for Apache JSPWiki, and as such subject to the usual voting guidelines: it
will be open for at least 72 hours, everybody is encouraged to vote,
although only PMC ones are binding.

[+1] yes, move to github as the primary repo
[0] don't mind
[-1] we are fine as it is now


best regards,
juan pablo

Re: Thoughts on how to increase contributions

[Juan Pablo Santos Rodríguez]

Hi,

just to make these things start moving,

* regarding moving to github as primary repo: infra needs a link to a
formal [VOTE] thread, so I'll begin one in a minute

* regarding committership, the examples provided weren't too accurate
** commons grants commit right to every asf committer on sandbox components
(https://wiki.apache.org/commons/CommonsEtiquette)
** subversion has the concept of partial committers (
https://subversion.apache.org/docs/community-guide/roles.html#partial-commit-access),
and also welcomes any asf committer to commit obvious fixes and patches, as
long as the patches have a +1 from a committer (
https://subversion.apache.org/docs/community-guide/roles.html#guest-commiter
)
** not asf related, but Jenkins does something similar (
https://jenkins.io/project/governance/#lower-barrier-of-entry): "by not
requiring new contributors to “prove themselves” before they are admitted
to the committership. Instead, we assume they are good until proven
otherwise"
** my take on this would be something similar to the jenkins model, but I'd
really appreciate first commits as PRs, for review.. At least that's what I
would do, but not sure if we should enforce this or just see how it unfolds
(given that we don't have much activity).. I suppose we would probably also
need a formal vote for this, but I'd like to ask what do other people think
about this before starting the vote

* regarding release trains (aka release every four months), as we have
Board reports on months 01, 04, 07 and 10, how about releasing on 02, 05,
08 and 11 (starting next 02)?


br,
juan pablo


On Tue, Nov 14, 2017 at 8:53 AM, Dave Koelmeyer <
dave.koelme...@davekoelmeyer.co.nz> wrote:

>
> On 10/11/17 09:57, Juan Pablo Santos Rodríguez wrote:
> > * Release at least every four months. Master is deliverable, and it's
> been
> > getting small fixes and updates every now and then so why not release
> every
> > (let's say) 4 months? They would be minor releases, but they still would
> be
> > releases, which would make JSPWiki a little better for end-users so,
> again,
> > why not? There could be exceptions if needed (i.e. master broken or no
> code
> > pushed since last release), but I think it would be a good thing(tm)
> Hi Juan Pablo
>
> Establishing regular releases would be fantastic. It would also be good
> source material for public-facing marketing material, and help set a
> clear message that the project is moving forward.
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.nz
> GPG Key ID: 0x238BFF87
>
>

Re: Data Migration

[Jürgen Weber]

Forgive my  ignorance. The old JDBCProvider has been ported and linked
by https://jspwiki-wiki.apache.org/Wiki.jsp?page=ContributedProviders

Jürgen

Re: Data Migration

[Jürgen Weber]

Col, will you port the old JDBCProvider?

Am 28.11.2017 16:56 schrieb "Col Willis" :

> I will look at that migratePlugin - Thanks.
>
> I thought of developing a Page Crawler using XML RPC; to re-create on the
> New Wiki.
>
> Is it possible to Download attachments/Files via the XMLRPC?
>
>
>
> On 28 November 2017 at 15:45, Jürgen Weber  wrote:
>
> > Well, there once was a JDBCProvider, might be fun to port it to current
> > JSPWiki ..
> >
> > License is LGPL.
> >
> > https://www.ecyrd.com/JSPWiki/wiki/JDBCProviders
> >
> > As for migrating, I once hacked a simple Plugin to migrate to a different
> > provider, it might be useful as copy template..
> >
> > https://github.com/weberjn/migratePlugin
> >
> > Jürgen
> >
> > Am 28.11.2017 14:16 schrieb "Col Willis" :
> >
> > > Hi all,
> > >
> > > I have a personal JSPWiki for a few years with File-based storage
> > > (jspwiki-files)
> > >
> > > I want to migrate this to AWS Cloud, but setup a Database back-end...
> > >
> > > What is the best way to Migrate data from jspwiki-files into Database?
> > >
> > >
> > > Thanks,
> > >
> > > Colin
> > >
> >
>
>
>
> --
> Col
>

Re: Data Migration

[Col Willis]

I will look at that migratePlugin - Thanks.

I thought of developing a Page Crawler using XML RPC; to re-create on the
New Wiki.

Is it possible to Download attachments/Files via the XMLRPC?



On 28 November 2017 at 15:45, Jürgen Weber  wrote:

> Well, there once was a JDBCProvider, might be fun to port it to current
> JSPWiki ..
>
> License is LGPL.
>
> https://www.ecyrd.com/JSPWiki/wiki/JDBCProviders
>
> As for migrating, I once hacked a simple Plugin to migrate to a different
> provider, it might be useful as copy template..
>
> https://github.com/weberjn/migratePlugin
>
> Jürgen
>
> Am 28.11.2017 14:16 schrieb "Col Willis" :
>
> > Hi all,
> >
> > I have a personal JSPWiki for a few years with File-based storage
> > (jspwiki-files)
> >
> > I want to migrate this to AWS Cloud, but setup a Database back-end...
> >
> > What is the best way to Migrate data from jspwiki-files into Database?
> >
> >
> > Thanks,
> >
> > Colin
> >
>



-- 
Col

Re: Data Migration

[Jürgen Weber]

Well, there once was a JDBCProvider, might be fun to port it to current
JSPWiki ..

License is LGPL.

https://www.ecyrd.com/JSPWiki/wiki/JDBCProviders

As for migrating, I once hacked a simple Plugin to migrate to a different
provider, it might be useful as copy template..

https://github.com/weberjn/migratePlugin

Jürgen

Am 28.11.2017 14:16 schrieb "Col Willis" :

> Hi all,
>
> I have a personal JSPWiki for a few years with File-based storage
> (jspwiki-files)
>
> I want to migrate this to AWS Cloud, but setup a Database back-end...
>
> What is the best way to Migrate data from jspwiki-files into Database?
>
>
> Thanks,
>
> Colin
>

Re: Data Migration

[Col Willis]

Of course!

On 28 November 2017 at 14:20, Paul Uszak  wrote:

> To be clear, you still want to stick with JSPWiki for the front end though?
>
> On 28 November 2017 at 13:16, Col Willis  wrote:
>
> > Hi all,
> >
> > I have a personal JSPWiki for a few years with File-based storage
> > (jspwiki-files)
> >
> > I want to migrate this to AWS Cloud, but setup a Database back-end...
> >
> > What is the best way to Migrate data from jspwiki-files into Database?
> >
> >
> > Thanks,
> >
> > Colin
> >
>



-- 
Col

Re: Data Migration

[Paul Uszak]

To be clear, you still want to stick with JSPWiki for the front end though?

On 28 November 2017 at 13:16, Col Willis  wrote:

> Hi all,
>
> I have a personal JSPWiki for a few years with File-based storage
> (jspwiki-files)
>
> I want to migrate this to AWS Cloud, but setup a Database back-end...
>
> What is the best way to Migrate data from jspwiki-files into Database?
>
>
> Thanks,
>
> Colin
>