Hey all,
Just closing the loop on this. I've migrated the wiki to:
https://cwiki.apache.org/confluence/display/SAMZA/Apache+Samza
The website has been updated accordingly.
Cheers,
Chris
On Wed, Feb 18, 2015 at 2:45 PM, Chris Riccomini
wrote:
> Hey all,
>
> I've setup a request with INFRA t
Hey all,
I've setup a request with INFRA to migrate to CWiki:
https://issues.apache.org/jira/browse/INFRA-9176
Cheers,
Chris
On Tue, Feb 17, 2015 at 9:57 AM, Yi Pan wrote:
> I shared the same pain with wiki before. Either cwiki or Markdown sounds
> good to me.
>
> -Yi
>
> On Tue, Feb 17, 2015
I shared the same pain with wiki before. Either cwiki or Markdown sounds
good to me.
-Yi
On Tue, Feb 17, 2015 at 9:53 AM, Chris Riccomini
wrote:
> Hey Milinda,
>
> Yea, I agree. Confluence is better than Moin Moin. If others agree, I think
> we should just switch to Confluence.
>
> So, shall we
Hey Milinda,
Yea, I agree. Confluence is better than Moin Moin. If others agree, I think
we should just switch to Confluence.
So, shall we block on Wiki upgrade? Probably will take a couple of days.
What do others thing about migrating to Confluence for wiki?
Cheers,
Chris
On Tue, Feb 17, 2015
Hi Chris,
I am okay with Markdown.
But we have the option of using cwiki (https://cwiki.apache.org). I have
used it in the past for Axis project. It's pretty flexible, with respect to
user management and I think its better than wiki deployed at wiki.apache.org.
For an example, you can give permis
Hey Milinda,
We can do wiki, but Apache's wiki is pretty locked down, sadly. You'll have
to get an account for it.
What if we just convert it to Markdown (like SAMZA-516), and attach to the
patch? This will make it versioned, and editable. Comments can happen in
the JIRA. I'm OK either way, but t
