Re: [Notion-devel] A git repo with ion/notion sources

[kevin g. <kev...@gm...>]

+1 for this approach (not that it matters, since you've already made
the git repo)

While this approach does mean duplicated effort, I think it has
promise just via its "just do it" attitude.  If we can make this
branch reach feature/stability parity with the other branch, then this
one will have the best of both worlds, especially since we should be
able to backport any changes made to the other branch to this one.  I
think the first order of business is to determine what exactly is
required to make this branch reach feature parity with the "bad
license" branch so we have a solid goal (in addition to the rename,
which should definitely happen due to the trademark issue).

I'm planning on cloning the repository and trying to come to grips
with what we need for feature parity tonight.

Kevin Granade

On Fri, Aug 27, 2010 at 9:14 AM, Joshua Tolley <egg...@gm...> wrote:
> On Fri, Aug 27, 2010 at 12:04:32AM +0300, Nedko Arnaudov wrote:
>> I personally think it is not worth to try to grow notion in a tainted
>> soil. Even if FSF replies that it is safe to use the latest codebase
>> after name change, it has yet to be proven in a court. And even then the
>> law depends on country.
>
> Can I register my bystander's support of at least exploring this option? I am
> unlikely ever to become an active ion/notion developer, and perhaps that
> changes the weight of my vote, but put me in the "interested user" category as
> one who over the years has tried without success to find an ion alternative.
> My particular concern, in fact, is not the licensing specifically, but is
> rather knowing that the project will remain active and easily available in
> common BSD or Linux distributions. An unfamiliar license makes both of those
> more difficult.
>
> That said, I don't honestly have any idea what differences there are between
> the latest code and this version, so I have no idea how much of a regression
> is involved if the project chooses this earlier codebase. Nor do I know how
> likely it is that, as the community begins modifying this earlier codebase,
> they would avoid adding code "tainted" by later ion versions. But those
> problems (and probably others I haven't thought of) need to be part of the
> discussion.
>
> --
> Joshua Tolley / eggyknap
> End Point Corporation
> http://www.endpoint.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkx3yCkACgkQRiRfCGf1UMM0QACgsL9g5iOPhpCp7lvsSzF5Znuf
> uPEAnAtD2Yt1z2mW65rkBD68h12tkhcS
> =fkS/
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Notion-devel mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-devel
>
>