Re: technical spec for the workstation up for review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]






----- Original Message -----
> From: "Jiri Eischmann" <eischmann@xxxxxxxxxx>
> To: desktop@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Thursday, February 20, 2014 10:42:24 AM
> Subject: Re: technical spec for the workstation up for review
> 
> Pete Travis píše v St 19. 02. 2014 v 12:16 -0700:
> > 
> > On Feb 18, 2014 2:24 PM, "Matthias Clasen" <mclasen@xxxxxxxxxx> wrote:
> > >
> > > I've spent quite a bit of time last week on this document:
> > > https://fedoraproject.org/wiki/Workstation/Technical_Specification
> > >
> > > It is not 100% complete, but I haven't found the time to get back to
> > it
> > > since Friday, so I should probably open it up for a first round of
> > > review to the other WG member.
> > >
> > > Let me know what you think,
> > >
> > > Matthias
> > >
> > > --
> > 
> > 
> > I realize it's early days and process must come before product, but I
> > was hoping to find something here that would differentiate between the
> > Workstation Product and the current/default GNOME desktop offering.
> > 
> > In my imagination, the user was asked what sort of development they
> > do, and appropriate packages were installed and settings applied. For
> > example, vim/emacs with helpful plugins configured, IDEs deployed,
> > compilers and libraries installed, some tooling like devassist or even
> > container integration for testing.   Is this more roadmap territory?
> > 
> > --Pete
> 
> Right, this is what DevAssistant does. You can easily create a project
> in your favourite language and DevAssistant does all the dirty work for
> you (installing packages you will most likely need for programming in
> that language, setting up an IDE, e.g. Vim or Eclipse, git, creating a
> project template etc.).
> If the main target group are developers, DevAssistant should be a big
> thing for the workstation product. I would even consider preinstalling
> it. Some integration with the rest of the desktop would be nice, too.
> For example GOA can support GitHub, OpenShift,... and then you don't
> have to set it up again in DevAssistant, but it can use GOA.
> What really makes a difference is not to have all pieces, but to have
> them nicely integrated to make a pleasant user experience.
> 
> Jiri

Just want to second Jiri here. The nice thing about doing an intergrated
product is that we can look at the system as a whole and plan based on that.
Which means that instead of trying to cram all kind of functionality into
the OS installer for instance, we can rely on things like the Software Installer
and the Developer Assistant to be part of the solution.

We should probably add a section to the technical specification talking
about DevAssistant and the kind of functionality we want to scope it for.

Christian



-- 
desktop mailing list
desktop@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/desktop





[Index of Archives]     [Fedora Users]     [Fedora KDE]     [Fedora Announce]     [Fedora Docs]     [Fedora Config]     [PAM]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux