On 24/10/16 16:09, Paul Houle wrote:
One reason why people have challenges communicating on mailing lists is
that English is not their first language.
I don't think English or not is that much of a factor so as much as
simply not reading the emails from the receivers point of view. It's
> The users@ list is about individuals and students are on the list as
> individuals, not as class participants. I fear discussion with the teachers
> could lead to serious problems - it would only take one large class, or even
> not so large class, pointed at users@ to take things to a whole di
From general reference
Apache has a code of conduct:
https://www.apache.org/foundation/policies/conduct
Just a couple of points to add to the discussion:
It would be a problem if we believe it is off putting for other people.
I don't think we are at that point but it is something to keep in m
I haven't seen anyone engaging in this discussion communicate any form of
racism.
The specific problem to which Colin Maudry referred is when questioners ignore
the responses to their questions. Language barriers are certainly a problem in
globally distributed work (having Jena documentation av
On 24/10/16 15:52, A. Soroka wrote:
I take the first bullet to mean some "enforcement" is proposed and the last bullet to suggest that
a "ban" is "possible".
Sorry, I missed that last phrase-- I wouldn't support a ban for that kind of reason. I
take "enforcement" simply to mean that after the
These arguments have a way of blending into racism.
One reason why people have challenges communicating on mailing lists is
that English is not their first language.
--
Paul Houle
paul.ho...@ontology2.com
On Mon, Oct 24, 2016, at 10:52 AM, A. Soroka wrote:
> > I take the first bullet to mea
> I take the first bullet to mean some "enforcement" is proposed and the last
> bullet to suggest that a "ban" is "possible".
Sorry, I missed that last phrase-- I wouldn't support a ban for that kind of
reason. I take "enforcement" simply to mean that after the same question is
asked several ti
On 24/10/16 14:48, A. Soroka wrote:
I'm a bit confused by some of the last few messages in this thread. I haven't
heard anyone suggesting that anyone be excluded from anything.
The title of this thread is "raising the bar".
The root post says:
"""
* inform the subscribers of an upcoming en
I'm a bit confused by some of the last few messages in this thread. I haven't
heard anyone suggesting that anyone be excluded from anything.
Dave and Rob are right to point out that projects go through phases. What's
more, the kind of communication appropriate to one phase may not be as useful
Hello Rob, Dave,
I agree that we should be flexible with learners and that not everyone
is supposed to “have years of experience of a software engineer and the
concept of MVCE drilled into them”.
But I assume that someone who takes the step to write to dozens of
strangers to ask for help is willi
I think these are excellent ideas, and I would love to help pursue them.
The current documentation does have tutorial-style sections, but there are lots
of other media at our disposal, e.g. as you say, video. A standard intro
webinar that could be arranged on a request basis would be pretty spec
Totally agree with Dave here
We always get phases of this kind of traffic. And whatever project you are
talking about there will always be users who try to run before they can walk.
This problem is not unique to our community, nor to the Apache foundation as a
whole. You will encounter this whe
There have been student questions on the jena users list since long
before Jena moved into Apache. While there's a burst at the moment I
don't see it as particularly worse than historic levels.
In the past sometimes teachers have stepped in and stopped it, sometimes
not.
I'm not convinced th
OK, I think that is a good idea to get in touch with the teachers; perhaps
so they can give us an advance notice and we can understand what their
course is meant to teach. So a more friendly request for the teachers to
get in touch (or we ask directly the name/email of their teacher), but
without t
> Then there are the obvious school examples, which seem to ask us the actual
> assignment rather than Jena questions. It is fair for us to dodge those, but
> perhaps in a less hostile way.
It seems to me that this is the entire question: there aren't really the kinds
of problems Colin Maudry
Agree to not go too aggressive in general, it could also strike down users
who like Jena as a tool (remember we have command lines and servers!) or
have been recommended Jena, but who have not before used Java as
programming language before. Here, tutorials and examples is what we should
point to.
I find this thread disturbing. Many people in the RDF community have
worked a long time and it's just recently that the uptake has broadened
(people are looking at JSON-LD and starting to understand what it means,
not what any particular authority says that it means, but what it
actually means.)
Andy has pointed to
https://stackoverflow.com/help/mcve
and I think it's a great starting place. On an additional note, there is a
clear pattern in the posts described very well by Colin Maudry-- the posters
are students doing school assignments. I have at least once suggested to at
least one
I must admit I find a number of the posts aggravating. So much so that I
stopped reading them long ago. I would support any effort to clean up the
questions and clearly mark messages that are not going to be answered.
Perhaps we should put together a page that clearly explains exactly what
data i
Dear Jena developers,
Upon Andy Seaborne’s suggestion, I would like to share with you a
concern we have with certain posts shared on us...@jena.apache.org.
In the last couple months, we have seen certain users repeatedly sending
questions that are either:
* hardly related to Jena and Fuseki
*
20 matches
Mail list logo
