I am aware. I'd say it doesn't (or shouldn't) apply in this case. Nobody is
taking a library out of SO and putting it into a project -- they don't have
such a thing. Reading a generic answer how to do something from a 5-line
code snippet, and then applying the (derivative) learning should not be
Hi,
> - We should -not- stress about whether SO is used by our contributors (to
> create contributions) and/or (its derivatives are) included in Apache
> projects.
Did you read currently legal policy on including CC-BY-SA licensed code? (not
matter where it comes from) It’s considered category
It feels this thread has somewhat veered off the initial question. My
position on this is non-purist, and perhaps more pragmatic.
SO licensing:
- Their licensing is reasonable for what they are trying to do. Just as
many social networks, they don't want somebody to suck up their (users')
content,
Craig
You are correct. I missed the distinction between their content and user
content.
As you say, nothing on SO can be incorporated into Apache anything without
separate licensing. This is a good argument for redundant answers on Apache
mailing lists.
On Sat, Apr 6, 2019, 6:45 AM Craig
> On Apr 5, 2019, at 8:03 PM, Justin Mclean wrote:
>
> Hi,
>
>> Not by my reading. Contributions to the content are licensed to SO by a
>> grant similar to the way contributions to Apache are licensed by a grant.
>> It's not copyright assignment, it's "just a grant.
>
> I believe they
Hi,
> Not by my reading. Contributions to the content are licensed to SO by a grant
> similar to the way contributions to Apache are licensed by a grant. It's not
> copyright assignment, it's "just a grant.
I believe they become a little more friendlier and it use to be that they did
own
Hi Ted,
> On Apr 5, 2019, at 3:08 PM, Ted Dunning wrote:
>
> Justin,
>
> THis is a huge and important point.
>
> I had completely forgotten that SO had these abusive terms.
>
> To summarize, just so everybody is clear, according to their terms of
> service *anything* you put on SO is the
I think we should get legal clarity if folks disagree, but providing
content under CC license does not stop you from also licensing it under ASL.
IOTW, I can give an answer, license that answer simultaneously to two
parties.
Agree that we cant lift other people's content from SO based on its
not saying it is practical but what I was getting at with the "also
licensing to ASF" thing would be a feature request to SO similar to github
contributing file integration.
ASF members could choose to license to ASF by default and have a badge put
on their content accordingly.
This doesn't
Justin,
THis is a huge and important point.
I had completely forgotten that SO had these abusive terms.
To summarize, just so everybody is clear, according to their terms of
service *anything* you put on SO is the property of SO. That is sooo
completely anti-Apache, that I have a hard time
Hi,
Sorry the bit I pasted doesn’t make sense on it’s own It should of started with
"for other than personal, noncommercial use is expressly prohibited …”
Thanks,
Justin
-
To unsubscribe, e-mail:
HI,
You also might want to note that anything contributed to stack overflow is
licensed under the CC-SA-3.0 [1] which may causes issues. [2] For instance code
from a stack overflow post can’t be included in a Apache project's code base.
In edition also note "noncommercial use is expressly
On Fri, 5 Apr 2019 at 15:58, Dave Fisher wrote:
>
> Hi -
>
> > On Apr 5, 2019, at 7:49 AM, Serge Huber wrote:
> >
> > If I may contribute my view here.
> >
> > Using StackOverflow is mostly great for StackOverflow. The more people go
> > there to post questions and get answers really helps
On Fri, Apr 5, 2019 at 6:35 AM James Bognar wrote:
> My $.02.
>
> Apache is sorely in need of a portal similar to StackOverflow. I,
> like many other software developers, primarily use Google for finding
> answers. 90% of the time those answers are going to be found on
> StackOverflow.
Hi -
> On Apr 5, 2019, at 7:49 AM, Serge Huber wrote:
>
> If I may contribute my view here.
>
> Using StackOverflow is mostly great for StackOverflow. The more people go
> there to post questions and get answers really helps mostly StackOverflow's
> bottom line. Also, StackOverflow does NOT
If I may contribute my view here.
Using StackOverflow is mostly great for StackOverflow. The more people go
there to post questions and get answers really helps mostly StackOverflow's
bottom line. Also, StackOverflow does NOT allow to simply link to sites for
answers, which is smart on their part
Hi,
On Fri, Apr 5, 2019 at 3:35 PM James Bognar wrote:
> ...Apache is sorely in need of a portal similar to StackOverflow...
What makes you think we need our own service, as opposed to helping
our users where they are?
As Ted said in this thread:
> Just subscribe to appropriate tags on stack
Agree with james.
Most of us search for an answer in Google.. which eventually take us to
stackoverflow.
Apache Mailing list answers are very rare in Google results.
Stackoverflow like portal could become next podling for incubator.
-Vinay
On Fri, 5 Apr 2019, 7:05 pm James Bognar, wrote:
>
My $.02.
Apache is sorely in need of a portal similar to StackOverflow. I,
like many other software developers, primarily use Google for finding
answers. 90% of the time those answers are going to be found on
StackOverflow. Answers on mailing lists are not going to show up in
Google results,
I sometimes used cut and paste in such cases. And if questions are
reflected into the dev or user, the duplications are apparent.
On Thu, Apr 4, 2019, 11:03 AM Julian Hyde wrote:
> It can be frustrating when someone posts a question to both the user list
> and to StackOverflow. It means that
Totally agreed with Julian here.
Community growth is one of the hardest aspects of a healthy, Apache
community. It is a never-ending and always-needed process. Shutting out
paths to growth, or partitioning where/how people might participate in the
community is a clear yellow flag. Reach out and
It can be frustrating when someone posts a question to both the user list and
to StackOverflow. It means that the community has to answer the question in two
places.
But like many problems, that is an opportunity. Answering StackOverflow
questions is a great way for people to contribute
Just subscribe to appropriate tags on stack overflow and direct
notifications to the dev list.
Then encourage the community to answer on stack overflow.
On Wed, Apr 3, 2019 at 6:32 PM Dave Fisher wrote:
> I think a user@ mailing list is better for the project’s sustainability
> and Apache.
>
I think a user@ mailing list is better for the project’s sustainability and
Apache.
I have examples related to POI where there is substantial StackOverflow support
happening.
12 years ago I became a POI committer for answering user questions.
Recently we asked an active StackOverflow answer
The superset podling is working out their processes around FAQs and
answering user questions. One thing that they have suggested is that they
encourage people to use StackOverflow for questions and answers given the
ease of searching old questions, etc. You can see the mail thread at
25 matches
Mail list logo
