All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexander.kanavin@linux.intel.com
To: "Andreas Oberritter" <obi@opendreambox.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: proposal: remove DirectFB from oe-core in the next release cycle
Date: Fri, 22 Jan 2016 21:10:31 +0200 (EET)	[thread overview]
Message-ID: <61461.10.252.10.201.1453489831.squirrel@linux.intel.com> (raw)
In-Reply-To: <56A26F89.8080505@opendreambox.org>

>> I guess the thing missing is an indication that the repo on github is
>> official and maintained.  Specifically the deniskropp repo has been
>> recently touched but you have to admit
>> that https://github.com/DirectFB/directfb looks more official.
>
> Denis Oliver Kropp is the main developer of DirectFB and the description
> of https://github.com/deniskropp/DirectFB says "Official DirectFB GitHub
> Repository".

Why did he make a new account on github then? Commits to the old directfb
repo were done from a different account (https://github.com/dfbdok). Also,
there has been no activity whatsoever since October, and no announcement
anywhere, and no response to my request or the other open issue in that
repo. I wouldn't trust that directfb is still alive; we need to wait and
see.

To me, it looks likely that the funding was cut, Denis Kropp has tried to
keep the project alive but then just abandoned it.

Alex


  parent reply	other threads:[~2016-01-22 18:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 12:58 proposal: remove DirectFB from oe-core in the next release cycle Alexander Kanavin
2016-01-22 13:04 ` Otavio Salvador
2016-01-22 15:38 ` Andreas Oberritter
2016-01-22 16:12   ` Burton, Ross
2016-01-22 18:06     ` Andreas Oberritter
2016-01-22 18:12       ` Burton, Ross
2016-01-22 19:10       ` alexander.kanavin [this message]
2016-01-22 18:49         ` Khem Raj
2016-02-01 10:21           ` Burton, Ross
2016-02-01 19:13             ` Andre McCurdy
2016-02-01 20:54               ` Burton, Ross
2016-01-22 18:47 ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61461.10.252.10.201.1453489831.squirrel@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=obi@opendreambox.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.