Re: Wicket site available in GitHub

I'm currently working with my intern to migrate the user guide to asciidoctor. He's a smart guy so it progresses quite impressively. We have a php script that migrates all docs from gdoc to asciidoc and are now in the process of generating a single HTML file and PDF. Multi page HTML site generatio

Re: Wicket site available in GitHub

Good see! What about the new site? - I remember that Martijn said that he wants it online when Wicket 7 is going to be released. The new one looks so awesome - can't wait. :-) kind regards Tobias > Am 17.06.2015 um 14:36 schrieb Martin Grigorov : > > Hi everyone, > > Since today the sources

Wicket site available in GitHub

Hi everyone, Since today the sources for http://wicket.apache.org/ are mirrored at https://github.com/apache/wicket-site. Pull requests with any kind of improvements are very welcome! Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov

Re: core devs cannot close PRs on github?

Yup. The integration between github and Apache are suboptimal. Infra is aware of the issue and wants to work on it. I have no insights into their plans, other than that they are in constant talks with github employees to improve the integration. Infra has been busy upgrading the services but they

Re: core devs cannot close PRs on github?

Hi, Yes. We don't have the permissions to do anything in the repositories. GitHub repos are just mirrors of the official Apache Git repositories. Only Apache Infrastructure team has write/admin rights there. Many people from Apache projects have asked Infra team for better support for

core devs cannot close PRs on github?

Hi, I notice that the core devs have to ask PR submitters to close their PRs on github: https://github.com/apache/wicket/pull/101 I am curious: Why is that so? Looking here: https://help.github.com/articles/permission-levels-for-an-organization-repository/ I assume the wicket core devs are

Re: GitHub

That's a GitHub question and not a Wicket one. Wrong mailing list. But here: https://help.github.com/articles/fork-a-repo/ 2014-11-13 20:58 GMT-05:00 Zala Pierre GOUPIL : > Hi all, > > When I try and fork Wicket github repo, I don't get all the branches and > tags.

GitHub

Hi all, When I try and fork Wicket github repo, I don't get all the branches and tags. Does anyone has a clue regarding that? Cheers, Pierre -- Si le sang ne coule pas assez chaud dans tes veines, je le répandrai sur le sable pour qu'il bouille au soleil.

Re: Which github branch

> Wicket github has both a 'master' & 'trunk'. Which one should I > choose? (or is there something else for 'latest 1.6.x code'?) It's currently still in master. Carl-Eric ---

Which github branch

I'm trying to work out which github branch to choose to stay up to date with the latest 1.6.x code. For wicket 1.5 I've just stuck with the 1.5.x branch and that worked well. There doesn't seem to be a 1.6.x - is this because 1.6 is the 'trunk' (in SVN speak). Wicket

Re: Github?

On Sat, Feb 25, 2012 at 6:17 PM, robmcguinness < robert.mcguinness@gmail.com> wrote: > I understand Apache has a git server where the Wicket trunk code is being > commited, but is there a reason why the Github account isn't being mirrored > properly? > I've

Re: http 500 status on GitHub

thank you & by the way, they fixed it in the meantime. mf Am 26.01.2011 um 21:00 schrieb Igor Vaynberg: > works for me :/ > > -igor > > On Wed, Jan 26, 2011 at 11:42 AM, Martin Funk > wrote: >> Hi, >> >> anyone experiencing something similar, as I described here? >> >> http://support.gi

Re: http 500 status on GitHub

works for me :/ -igor On Wed, Jan 26, 2011 at 11:42 AM, Martin Funk wrote: > Hi, > > anyone experiencing something similar, as I described here? > > http://support.github.com/discussions/site/2640-wiki-git-access-leads-to-500 > > mf > > ---

http 500 status on GitHub

Hi, anyone experiencing something similar, as I described here? http://support.github.com/discussions/site/2640-wiki-git-access-leads-to-500 mf - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional comman

[Announce] Migration of wicketstuff from sourceforge to github is now complete

Hello, I am pleased to announce that the migration of the wicketstuff project from sourceforge to github is now complete. Developers will again be able to commit their changes (pending registration as a committer); Users will be able to report their issues and new documentation can start to

Re: Moving wicketstuff to github

Martijn, > > can we commit to wicketstuff again? If so, where: sf.net or github? > > Regards, > > Seb > > On 23.12.2010 11:04, Martijn Dashorst wrote: >> >> All, >> >> Last week we (wicket+wicketstuff devs) had a discussion on dev@ and >> decided

Re: Moving wicketstuff to github

Hi Martijn, can we commit to wicketstuff again? If so, where: sf.net or github? Regards, Seb On 23.12.2010 11:04, Martijn Dashorst wrote: All, Last week we (wicket+wicketstuff devs) had a discussion on dev@ and decided to move all wicketstuff code to github.com. Reasons to move to github

Moving wicketstuff to github

All, Last week we (wicket+wicketstuff devs) had a discussion on dev@ and decided to move all wicketstuff code to github.com. Reasons to move to github are: - using git - social features for interacting with grander community (merging, pull requests, forking) - integrated wiki, issue tracker