5:16 a.m.
= Features/DevelopersAssistant =
https://fedoraproject.org/wiki/Features/DevelopersAssistant
Feature owner(s): Jan Zelený <jzeleny(a)redhat.com>, Marcela Mašláňová
<mmaslano(a)redhat.com>
Perform a series of various changes to improve developer experience on Fedora.
== Detailed description ==
This feature aims on setting up development environment for various languages.
Target groups include beginning developers but also experienced developers not
used to GNU/Linux as well as experienced Linux developers not used to Fedora.
This feature will cover a basic set of tasks which will prepare Fedora for
later additions. The first part of the feature is a review of comps groups
which would lead to better granularity of package sets necessary for
development in different languages. Another part is about providing tool or
tools for simple start of a project in terms of creating project template
based on different languages and/or frameworks which the project should use.
There are other optional activities like vim/eclipse/emacs/... plugins,
integration of rpm build tools, .... These optional parts are not goal for F19
but they will be integrated in time.
Languages:
C (phracek)
Ruby (vondruch)
Python (bkabrda)
Perl (mmaslano)
PHP (rcollet)
Java (msrb)
Javascript
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
6:57 a.m.
On Mon, Jan 28, 2013 at 6:16 AM, Jaroslav Reznik <jreznik(a)redhat.com> wrote:
= Features/DevelopersAssistant =
https://fedoraproject.org/wiki/Features/DevelopersAssistant
Feature owner(s): Jan Zelený <jzeleny(a)redhat.com>, Marcela Mašláňová
<mmaslano(a)redhat.com>
Perform a series of various changes to improve developer experience on Fedora.
== Detailed description ==
This feature aims on setting up development environment for various languages.
Target groups include beginning developers but also experienced developers not
used to GNU/Linux as well as experienced Linux developers not used to Fedora.
This feature will cover a basic set of tasks which will prepare Fedora for
later additions. The first part of the feature is a review of comps groups
which would lead to better granularity of package sets necessary for
development in different languages. Another part is about providing tool or
tools for simple start of a project in terms of creating project template
based on different languages and/or frameworks which the project should use.
I'm not sure what the "tool or tools" part is supposed to cover. Could
someone give an example of one of these new setup leaf packages?
josh
8:27 a.m.
On 28. 1. 2013 at 07:57:11, Josh Boyer wrote:
On Mon, Jan 28, 2013 at 6:16 AM, Jaroslav Reznik
<jreznik(a)redhat.com> wrote:
> = Features/DevelopersAssistant =
> https://fedoraproject.org/wiki/Features/DevelopersAssistant
>
> Feature owner(s): Jan Zelený <jzeleny(a)redhat.com>, Marcela Mašláňová
> <mmaslano(a)redhat.com>
>
> Perform a series of various changes to improve developer experience on
> Fedora.
>
> == Detailed description ==
> This feature aims on setting up development environment for various
> languages. Target groups include beginning developers but also
> experienced developers not used to GNU/Linux as well as experienced Linux
> developers not used to Fedora.
>
> This feature will cover a basic set of tasks which will prepare Fedora for
> later additions. The first part of the feature is a review of comps groups
> which would lead to better granularity of package sets necessary for
> development in different languages. Another part is about providing tool
> or
> tools for simple start of a project in terms of creating project template
> based on different languages and/or frameworks which the project should
> use.
I'm not sure what the "tool or tools" part is supposed to cover. Could
someone give an example of one of these new setup leaf packages?
josh
Currently we are working on some proof-of-concept stuff. But as an example, you
can imagine a script for creation of C program templates. You will specify
directory where it should create the program and (possibly) some specifics,
like "I want to use threads" or "I need glib support".
On output of that script you will have a template of C program with Makefile
and you can start coding right away, no need for preparing the environment
first.
Please note that scope of this feature is not limited and by design this
entire effort is not limited. We want to start with a bunch of scripts which
will be then integrated as modules into one command (to make it easy to
remember).
We are not yet sure how many packages are we talking about here, it might as
well be just one package containing all the scripts and each script will check
for presence of specific prerequisities already packaged somewhere else. Or
every script can be a part of already existing package (similar to bash
completion scripts). As these are leaf packages (nothing will depend on them),
the only important part of the design is not to completely change the approach
in the future.
If you have any other questions or concerns, feel free to ask.
Thanks
Jan
11:48 a.m.
Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
Currently we are working on some proof-of-concept stuff. But as an example, you
can imagine a script for creation of C program templates. You will specify
directory where it should create the program and (possibly) some specifics,
like "I want to use threads" or "I need glib support".
On output of that script you will have a template of C program with Makefile
and you can start coding right away, no need for preparing the environment
first.
Something like https://wiki.ubuntu.com/Quickly ?
Some work have been started by Mathieu bridon and Didier Roche for
quickly on Fedora a few years ago. Not sure where it went, but this
would be easier to use it rather than start from scratch.
--
Michael Scherer
1:28 p.m.
Michael Scherer (misc(a)zarb.org) said:
Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
>
> Currently we are working on some proof-of-concept stuff. But as an example, you
> can imagine a script for creation of C program templates. You will specify
> directory where it should create the program and (possibly) some specifics,
> like "I want to use threads" or "I need glib support".
>
> On output of that script you will have a template of C program with Makefile
> and you can start coding right away, no need for preparing the environment
> first.
Something like https://wiki.ubuntu.com/Quickly ?
Some work have been started by Mathieu bridon and Didier Roche for
quickly on Fedora a few years ago. Not sure where it went, but this
would be easier to use it rather than start from scratch.
Do we know whether our target users for these quick-onroad scripts are using
the commandline vs something like Eclipse? Just curious where the
bang-for-the-buck is.
Bill
2:14 a.m.
On 28. 1. 2013 at 14:28:06, Bill Nottingham wrote:
Michael Scherer (misc(a)zarb.org) said:
> Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> > Currently we are working on some proof-of-concept stuff. But as an
> > example, you can imagine a script for creation of C program templates.
> > You will specify directory where it should create the program and
> > (possibly) some specifics, like "I want to use threads" or "I
need glib
> > support".
> >
> > On output of that script you will have a template of C program with
> > Makefile and you can start coding right away, no need for preparing the
> > environment first.
>
> Something like https://wiki.ubuntu.com/Quickly ?
>
> Some work have been started by Mathieu bridon and Didier Roche for
> quickly on Fedora a few years ago. Not sure where it went, but this
> would be easier to use it rather than start from scratch.
Do we know whether our target users for these quick-onroad scripts are using
the commandline vs something like Eclipse? Just curious where the
bang-for-the-buck is.
Actually we want to address both. Use cases for Eclipse users will be
addressed in second stage of the project, hopefully utilizing whatever we
produce.
Thanks
Jan
12:18 p.m.
On Tue, Jan 29, 2013 at 9:14 AM, Jan Zelený <jzeleny(a)redhat.com> wrote:
On 28. 1. 2013 at 14:28:06, Bill Nottingham wrote:
> Michael Scherer (misc(a)zarb.org) said:
> > Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> > > Currently we are working on some proof-of-concept stuff. But as an
> > > example, you can imagine a script for creation of C program templates.
> > > You will specify directory where it should create the program and
> > > (possibly) some specifics, like "I want to use threads" or
"I need glib
> > > support".
> > >
> > > On output of that script you will have a template of C program with
> > > Makefile and you can start coding right away, no need for preparing the
> > > environment first.
> >
> > Something like https://wiki.ubuntu.com/Quickly ?
> >
> > Some work have been started by Mathieu bridon and Didier Roche for
> > quickly on Fedora a few years ago. Not sure where it went, but this
> > would be easier to use it rather than start from scratch.
>
> Do we know whether our target users for these quick-onroad scripts are using
> the commandline vs something like Eclipse? Just curious where the
> bang-for-the-buck is.
Actually we want to address both. Use cases for Eclipse users will be
addressed in second stage of the project, hopefully utilizing whatever we
produce.
Eclipse already has some of this, see e.g.
http://wiki.eclipse.org/CDT/Autotools/User_Guide .
Mirek
1:22 a.m.
On 29. 1. 2013 at 19:18:32, Miloslav Trmač wrote:
On Tue, Jan 29, 2013 at 9:14 AM, Jan Zelený
<jzeleny(a)redhat.com> wrote:
> On 28. 1. 2013 at 14:28:06, Bill Nottingham wrote:
>> Michael Scherer (misc(a)zarb.org) said:
>> > Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
>> > > Currently we are working on some proof-of-concept stuff. But as an
>> > > example, you can imagine a script for creation of C program
>> > > templates.
>> > > You will specify directory where it should create the program and
>> > > (possibly) some specifics, like "I want to use threads" or
"I need
>> > > glib
>> > > support".
>> > >
>> > > On output of that script you will have a template of C program with
>> > > Makefile and you can start coding right away, no need for preparing
>> > > the
>> > > environment first.
>> >
>> > Something like https://wiki.ubuntu.com/Quickly ?
>> >
>> > Some work have been started by Mathieu bridon and Didier Roche for
>> > quickly on Fedora a few years ago. Not sure where it went, but this
>> > would be easier to use it rather than start from scratch.
>>
>> Do we know whether our target users for these quick-onroad scripts are
>> using the commandline vs something like Eclipse? Just curious where the
>> bang-for-the-buck is.
>
> Actually we want to address both. Use cases for Eclipse users will be
> addressed in second stage of the project, hopefully utilizing whatever we
> produce.
Eclipse already has some of this, see e.g.
http://wiki.eclipse.org/CDT/Autotools/User_Guide .
I thought so, even though I didn't do much research on this front. Thanks for
the link, I'll check it out.
Jan
1:50 a.m.
Jan Zelený píše v St 30. 01. 2013 v 08:22 +0100:
On 29. 1. 2013 at 19:18:32, Miloslav Trmač wrote:
> On Tue, Jan 29, 2013 at 9:14 AM, Jan Zelený <jzeleny(a)redhat.com> wrote:
> > On 28. 1. 2013 at 14:28:06, Bill Nottingham wrote:
> >> Michael Scherer (misc(a)zarb.org) said:
> >> > Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> >> > > Currently we are working on some proof-of-concept stuff. But as
an
> >> > > example, you can imagine a script for creation of C program
> >> > > templates.
> >> > > You will specify directory where it should create the program
and
> >> > > (possibly) some specifics, like "I want to use threads"
or "I need
> >> > > glib
> >> > > support".
> >> > >
> >> > > On output of that script you will have a template of C program
with
> >> > > Makefile and you can start coding right away, no need for
preparing
> >> > > the
> >> > > environment first.
> >> >
> >> > Something like https://wiki.ubuntu.com/Quickly ?
> >> >
> >> > Some work have been started by Mathieu bridon and Didier Roche for
> >> > quickly on Fedora a few years ago. Not sure where it went, but this
> >> > would be easier to use it rather than start from scratch.
> >>
> >> Do we know whether our target users for these quick-onroad scripts are
> >> using the commandline vs something like Eclipse? Just curious where the
> >> bang-for-the-buck is.
> >
> > Actually we want to address both. Use cases for Eclipse users will be
> > addressed in second stage of the project, hopefully utilizing whatever we
> > produce.
>
> Eclipse already has some of this, see e.g.
> http://wiki.eclipse.org/CDT/Autotools/User_Guide .
I thought so, even though I didn't do much research on this front. Thanks for
the link, I'll check it out.
From my knowledge every good IDE has its own kind of "developer
assistant" so IMHO it would be hard to come up with an universal
concept. And not everyone uses Eclipse ...
Dan
2:58 a.m.
On 30. 1. 2013 at 08:50:23, Dan Horák wrote:
Jan Zelený píše v St 30. 01. 2013 v 08:22 +0100:
> On 29. 1. 2013 at 19:18:32, Miloslav Trmač wrote:
> > On Tue, Jan 29, 2013 at 9:14 AM, Jan Zelený <jzeleny(a)redhat.com> wrote:
> > > On 28. 1. 2013 at 14:28:06, Bill Nottingham wrote:
> > >> Michael Scherer (misc(a)zarb.org) said:
> > >> > Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> > >> > > Currently we are working on some proof-of-concept stuff. But
as
> > >> > > an
> > >> > > example, you can imagine a script for creation of C program
> > >> > > templates.
> > >> > > You will specify directory where it should create the
program and
> > >> > > (possibly) some specifics, like "I want to use
threads" or "I
> > >> > > need
> > >> > > glib
> > >> > > support".
> > >> > >
> > >> > > On output of that script you will have a template of C
program
> > >> > > with
> > >> > > Makefile and you can start coding right away, no need for
> > >> > > preparing
> > >> > > the
> > >> > > environment first.
> > >> >
> > >> > Something like https://wiki.ubuntu.com/Quickly ?
> > >> >
> > >> > Some work have been started by Mathieu bridon and Didier Roche
for
> > >> > quickly on Fedora a few years ago. Not sure where it went, but
this
> > >> > would be easier to use it rather than start from scratch.
> > >>
> > >> Do we know whether our target users for these quick-onroad scripts
> > >> are
> > >> using the commandline vs something like Eclipse? Just curious where
> > >> the
> > >> bang-for-the-buck is.
> > >
> > > Actually we want to address both. Use cases for Eclipse users will be
> > > addressed in second stage of the project, hopefully utilizing whatever
> > > we
> > > produce.
> >
> > Eclipse already has some of this, see e.g.
> > http://wiki.eclipse.org/CDT/Autotools/User_Guide .
>
> I thought so, even though I didn't do much research on this front. Thanks
> for the link, I'll check it out.
From my knowledge every good IDE has its own kind of "developer
assistant" so IMHO it would be hard to come up with an universal
concept. And not everyone uses Eclipse ...
Yes, I know that but these are usually IDE specific (you have to build/run your
project directly from the IDE). This might serve as a common way of doing
things in IDE and on CLI. It won't be as advanced as those assistants in IDEs
but then again - that's not our goal, just some basic support will do for now.
Those who don't use Eclipse will still have the CLI toolset we are working on
right now. Also we don't prevent anyone to come and build support for other
IDEs :-)
Thanks
Jan
3:07 a.m.
----- Original Message -----
From: "Jan Zelený" <jzeleny(a)redhat.com>
To: devel(a)lists.fedoraproject.org
Cc: "Miloslav Trmač" <mitr(a)volny.cz>
Sent: Wednesday, January 30, 2013 9:22:07 AM
Subject: Re: Proposed F19 Feature: Developers Assistant
On 29. 1. 2013 at 19:18:32, Miloslav Trmač wrote:
> On Tue, Jan 29, 2013 at 9:14 AM, Jan Zelený <jzeleny(a)redhat.com>
> wrote:
> > On 28. 1. 2013 at 14:28:06, Bill Nottingham wrote:
> >> Michael Scherer (misc(a)zarb.org) said:
> >> > Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> >> > > Currently we are working on some proof-of-concept stuff. But
> >> > > as an
> >> > > example, you can imagine a script for creation of C program
> >> > > templates.
> >> > > You will specify directory where it should create the
> >> > > program and
> >> > > (possibly) some specifics, like "I want to use threads"
or
> >> > > "I need
> >> > > glib
> >> > > support".
> >> > >
> >> > > On output of that script you will have a template of C
> >> > > program with
> >> > > Makefile and you can start coding right away, no need for
> >> > > preparing
> >> > > the
> >> > > environment first.
> >> >
> >> > Something like https://wiki.ubuntu.com/Quickly ?
> >> >
> >> > Some work have been started by Mathieu bridon and Didier Roche
> >> > for
> >> > quickly on Fedora a few years ago. Not sure where it went, but
> >> > this
> >> > would be easier to use it rather than start from scratch.
> >>
> >> Do we know whether our target users for these quick-onroad
> >> scripts are
> >> using the commandline vs something like Eclipse? Just curious
> >> where the
> >> bang-for-the-buck is.
> >
> > Actually we want to address both. Use cases for Eclipse users
> > will be
> > addressed in second stage of the project, hopefully utilizing
> > whatever we
> > produce.
>
> Eclipse already has some of this, see e.g.
> http://wiki.eclipse.org/CDT/Autotools/User_Guide .
I thought so, even though I didn't do much research on this front.
Thanks for
the link, I'll check it out.
Hi,
Eclipse is one step ahead on this already. FYI
http://rgrunber.fedorapeople.org/eclipse_packagekit_2.ogv and
http://rgrunber.fedorapeople.org/eclipse_packagekit_2.ogv .
Having IDE users as a post-thought never works - either one tool is thought with both kind
console and ide users from the beginning or it will stay console or ide only. Simply
wrapping console calls with some UI doesn't work because you need to make the tool
work in a familiar way for the group you target.
I would be happy to join such conversations so please either add me to any mails flowing
on the topic or tell me if there is some mailing list to join.
Alexander Kurtakov
Red Hat Eclipse team
Jan
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
2:14 a.m.
On 28. 1. 2013 at 18:48:41, Michael Scherer wrote:
Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> Currently we are working on some proof-of-concept stuff. But as an
> example, you can imagine a script for creation of C program templates.
> You will specify directory where it should create the program and
> (possibly) some specifics, like "I want to use threads" or "I need
glib
> support".
>
> On output of that script you will have a template of C program with
> Makefile and you can start coding right away, no need for preparing the
> environment first.
Something like https://wiki.ubuntu.com/Quickly ?
Yes, Quickly is the origin of this idea.
Some work have been started by Mathieu bridon and Didier Roche for
quickly on Fedora a few years ago. Not sure where it went, but this
would be easier to use it rather than start from scratch.
Sounds interesting, if we could somehow utilize this, it would be a great
starting point.
Thanks
Jan
5:27 a.m.
----- Original Message -----
Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
>
> Currently we are working on some proof-of-concept stuff. But as an
> example, you
> can imagine a script for creation of C program templates. You will
> specify
> directory where it should create the program and (possibly) some
> specifics,
> like "I want to use threads" or "I need glib support".
>
> On output of that script you will have a template of C program with
> Makefile
> and you can start coding right away, no need for preparing the
> environment
> first.
Something like https://wiki.ubuntu.com/Quickly ?
And I'd say - not only Quickly as a tool but what do we need more is
something like http://developer.ubuntu.com/ (and yes, Quickly is part
of it). Same did Nokia with Harmattan Developer web.
Documentation, how to start (based on the tools we provide), guides,
how to's should be the main part of this effort.
Jaroslav
Some work have been started by Mathieu bridon and Didier Roche for
quickly on Fedora a few years ago. Not sure where it went, but this
would be easier to use it rather than start from scratch.
--
Michael Scherer
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
5:37 a.m.
On 30. 1. 2013 at 06:27:48, Jaroslav Reznik wrote:
----- Original Message -----
> Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> > Currently we are working on some proof-of-concept stuff. But as an
> > example, you
> > can imagine a script for creation of C program templates. You will
> > specify
> > directory where it should create the program and (possibly) some
> > specifics,
> > like "I want to use threads" or "I need glib support".
> >
> > On output of that script you will have a template of C program with
> > Makefile
> > and you can start coding right away, no need for preparing the
> > environment
> > first.
>
> Something like https://wiki.ubuntu.com/Quickly ?
And I'd say - not only Quickly as a tool but what do we need more is
something like http://developer.ubuntu.com/ (and yes, Quickly is part
of it). Same did Nokia with Harmattan Developer web.
Documentation, how to start (based on the tools we provide), guides,
how to's should be the main part of this effort.
I've already started to work on that as well. Currently I'm putting together
topics from Fedora wiki that are eligible to be on such page, either as they
are or with some (rather minor) modifications.
I'd like them to be structured, easy to comprehend and most importantly as
short as possible.
If you know any such topic, feel free to let me know.
Thanks
Jan
5:54 a.m.
----- Original Message -----
On 30. 1. 2013 at 06:27:48, Jaroslav Reznik wrote:
> ----- Original Message -----
>
> > Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> > > Currently we are working on some proof-of-concept stuff. But as
> > > an
> > > example, you
> > > can imagine a script for creation of C program templates. You
> > > will
> > > specify
> > > directory where it should create the program and (possibly)
> > > some
> > > specifics,
> > > like "I want to use threads" or "I need glib
support".
> > >
> > > On output of that script you will have a template of C program
> > > with
> > > Makefile
> > > and you can start coding right away, no need for preparing the
> > > environment
> > > first.
> >
> > Something like https://wiki.ubuntu.com/Quickly ?
>
> And I'd say - not only Quickly as a tool but what do we need more
> is
> something like http://developer.ubuntu.com/ (and yes, Quickly is
> part
> of it). Same did Nokia with Harmattan Developer web.
>
> Documentation, how to start (based on the tools we provide),
> guides,
> how to's should be the main part of this effort.
I've already started to work on that as well. Currently I'm putting
together
topics from Fedora wiki that are eligible to be on such page, either
as they
are or with some (rather minor) modifications.
I'd like them to be structured, easy to comprehend and most
importantly as
short as possible.
Would you need anything from Design/Web team to support it?
Jaroslav
If you know any such topic, feel free to let me know.
Thanks
Jan
6:02 a.m.
On 30. 1. 2013 at 06:54:14, Jaroslav Reznik wrote:
----- Original Message -----
> On 30. 1. 2013 at 06:27:48, Jaroslav Reznik wrote:
> > ----- Original Message -----
> >
> > > Le lundi 28 janvier 2013 à 15:27 +0100, Jan Zelený a écrit :
> > > > Currently we are working on some proof-of-concept stuff. But as
> > > > an
> > > > example, you
> > > > can imagine a script for creation of C program templates. You
> > > > will
> > > > specify
> > > > directory where it should create the program and (possibly)
> > > > some
> > > > specifics,
> > > > like "I want to use threads" or "I need glib
support".
> > > >
> > > > On output of that script you will have a template of C program
> > > > with
> > > > Makefile
> > > > and you can start coding right away, no need for preparing the
> > > > environment
> > > > first.
> > >
> > > Something like https://wiki.ubuntu.com/Quickly ?
> >
> > And I'd say - not only Quickly as a tool but what do we need more
> > is
> > something like http://developer.ubuntu.com/ (and yes, Quickly is
> > part
> > of it). Same did Nokia with Harmattan Developer web.
> >
> > Documentation, how to start (based on the tools we provide),
> > guides,
> > how to's should be the main part of this effort.
>
> I've already started to work on that as well. Currently I'm putting
> together
> topics from Fedora wiki that are eligible to be on such page, either
> as they
> are or with some (rather minor) modifications.
>
> I'd like them to be structured, easy to comprehend and most
> importantly as
> short as possible.
Would you need anything from Design/Web team to support it?
Jaroslav
Yes, probably. But it's not that critical at this moment. First we need a
content, then design and other stuff ;-)
Thanks
Jan
2:54 p.m.
Jan Zelený (jzeleny(a)redhat.com) said:
I've already started to work on that as well. Currently I'm
putting together
topics from Fedora wiki that are eligible to be on such page, either as they
are or with some (rather minor) modifications.
I'd like them to be structured, easy to comprehend and most importantly as
short as possible.
If you know any such topic, feel free to let me know.
Does this go all the way into "libraries you should use" and "libraries
you
shouldn't"?
Bill
2:34 a.m.
On 30. 1. 2013 at 15:54:25, Bill Nottingham wrote:
Jan Zelený (jzeleny(a)redhat.com) said:
> I've already started to work on that as well. Currently I'm putting
> together topics from Fedora wiki that are eligible to be on such page,
> either as they are or with some (rather minor) modifications.
>
> I'd like them to be structured, easy to comprehend and most importantly as
> short as possible.
>
> If you know any such topic, feel free to let me know.
Does this go all the way into "libraries you should use" and "libraries
you
shouldn't"?
Bill
Well, that's slightly advanced topic but I think we can arrange something like
advanced section on the Developers' portal.
Is this already somewhere on the Fedora wiki?
Thanks
Jan
10:17 a.m.
Jan Zelený (jzeleny(a)redhat.com) said:
> Does this go all the way into "libraries you should
use" and "libraries you
> shouldn't"?
Well, that's slightly advanced topic but I think we can arrange something like
advanced section on the Developers' portal.
Is this already somewhere on the Fedora wiki?
No, it would be useful information to have.
Bill
4133
days inactive
4136
days old
18 comments
8 participants
participants (8)
-
Aleksandar Kurtakov -
Bill Nottingham -
Dan Horák -
Jan Zelený -
Jaroslav Reznik -
Josh Boyer -
Michael Scherer -
Miloslav Trmač