+1 for that useage (and not for documentation).
I'm a big wiki fan too, for quick documents.
(I do all my teaching "web" pages using a wiki now.)
On 8/8/15 1:31 AM, Ted Dunning wrote:
They might well work for that.
On Sat, Aug 8, 2015 at 12:53 AM, Till Westmann <[email protected]> wrote:
In general I'm also not a big fan of Wikis as they tend to get messy after
a while.
So I wouldn't necessarily use them for documentation. But I think that
there's a place for them for quick collaboration.
Do you think that the Apache Wikis (confluence in this case) would be
suited for that or would that be cumbersome as well?
On 8 Aug 2015, at 0:46, Ted Dunning wrote:
Be cautious a bit here. The wikis that are available at Apache tend to be
a bit cumbersome.
Some projects have lately opted to simply storing pages as mark-down which
are automatically rendered. This makes it easy to make updates and even
have outsiders contributed, but not as easy as a wiki. On the other hand,
it is more reliable and serves pages very fast.
On Sat, Aug 8, 2015 at 12:33 AM, Till Westmann <[email protected]> wrote:
I've created a request (
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-10090
),
hopefully the information I provided is sufficient.
Cheers,
Till
On 8 Aug 2015, at 0:11, Jianfeng Jia wrote:
+1 for wiki!
On Sat, Aug 8, 2015 at 12:09 AM, abdullah alamoudi <[email protected]>
wrote:
I agree with both of you. This is not a single man job :-)
On Sat, Aug 8, 2015 at 10:06 AM, Till Westmann <[email protected]>
wrote:
We don't have a wiki yet, but it should be easy to get one (and it's
probably the right tool to do something like this).
Would you agree?
Cheers,
Till
On 7 Aug 2015, at 23:59, Jianfeng Jia wrote:
Do you guys like the Wiki? like the Spark's:
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark
.
We can create a skeleton, create different pages for different
internal
components, and *gradually* fill it. (It's a history debt that I
don't
think some guy can spend just some days to finish it perfectly. Let's
crowdsource it. :-)
On Fri, Aug 7, 2015 at 11:04 PM, abdullah alamoudi <
[email protected]
wrote:
Hi everyone,
In the August 2015 incubator report, the 3rd issue to address before
graduation is growing the AsterixDB community.
Since we entered the incubator, at least two members wanted to join
the
community and contribute only to end up disappearing. Getting
acquainted
with the codebase seems like a difficult task for new comers and I
think
we
should make it a little bit easier.
I know this is long overdue and someone promised in the ancient past
to
prepare an entry document for new contributor (Who was it?). I am
aware
that we all are busy addressing issues, working on new features,
running
some experiments, writing a paper, etc. but we can still work towards
this
in small steps.
My suggestion is that someone create an outline of how that document
will
be and then publish it in some location where we all have a chance to
contribute (Maybe the AsterixDB website in the documentation
branch?).
Once
we have that, whenever somebody spends some time in a new area of
the
code,
they should contribute to the document and we should eventually get
there.
Cheers,
Amoudi, Abdullah.
--
-----------------
Best Regards
Jianfeng Jia
Ph.D. Candidate of Computer Science
University of California, Irvine
--
Amoudi, Abdullah.
--
-----------------
Best Regards
Jianfeng Jia
Ph.D. Candidate of Computer Science
University of California, Irvine
