<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/27/2015 06:41 AM, Nick Coghlan
wrote:<br>
</div>
<blockquote cite="mid:55B5B684.2020304@redhat.com" type="cite">
<pre wrap="">On 07/24/2015 07:16 PM, Adam Samalik wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Nick,
thanks!
What I'm still missing in the current prototype is the "problem to be solved" starting point - as you pointed out at the env-and-stacks meeting. For example: I want to develop a web application. The site would give me options like Django, Flask, Ruby on Rails, PHP, Jekyll,... Or even better, something more precise like deciding the type of the web app: an application with backend and database, a static site, blog or a wiki page? The tech-specific overview would show up afterwards. Suitable tools and deployment option would show up as well. What do you think?
</pre>
</blockquote>
<pre wrap="">
I think it probably makes sense to focus on <a class="moz-txt-link-freetext" href="http://devassistant.org/">http://devassistant.org/</a> and
<a class="moz-txt-link-freetext" href="https://dapi.devassistant.org/">https://dapi.devassistant.org/</a> as the entry points to the Fedora
developer experience. We may want to pick out particular assistants and
highlight them (especially if we design the Fedora DA package to come
with some assistants pre-installed), but I think it makes sense to push
the "comprehensive" side of the story further upstream, and have
developers.fedoraproject.org present a more filtered view, just as the
main Fedora repos represent a filtered view of the upstream software
repositories.</pre>
</blockquote>
Yeah Nick, many of the things can be done by DA. But some have to
create assistants.<br>
But I think then documentation and especially web pages are useful<br>
for this case.<br>
<br>
I think that some sections in developer.fedoraproject.org, like<br>
Python, Ruby, Docker, should contain a row how we can use DA for it.<br>
<blockquote cite="mid:55B5B684.2020304@redhat.com" type="cite">
<pre wrap="">
My rationale for that is that DA provides an abstraction layer over
various mundane technical details - if you're using a well-maintained DA
Assistant to automate setting up a particular kind of project, then your
own practices can automatically adapt as recommendations change. If
folks want to learn more about the details of a recommendation, they can
dig into the implementation of the relevant assistant, but if they don't
want to care, they don't have to.
The DA folks are also actively working on offering good support for the
"Container Tools" workflow coming out of Project Atomic - that's a
Vagrant+containers based approach designed to be cross-platform for
development purposes and cross-distro for both development and
deployment, so adopting it for web service development means folks are
automatically lowering the barriers to entry to contributing to and
deploying their project. That workflow also actively encourages folks to
clearly separate their unit testing from their behavioural testing.
Given a default assumption that folks are willing to use DevAssistant
(either through the GUI or through the CLI), then the following kinds of
questions could help guide site users to appropriate assistants:
* I want to build a web application, where do I start?
* I want to build a command line application, where do I start?
* I want to build a desktop GUI application, where do I start?
* I want to build a mobile application, where do I start?
* I want to work with the Raspberry Pi, where do I start?
* I want to work with Arduino devices, where do I start?
* I want to work with other embedded devices, where do I start?
* I want to provide online documentation for my project, where do I start?
* I want to collaborate effectively with others on my project, where do
I start?
</pre>
</blockquote>
Right, but developer.fp.org is not about DA. It should be for users
how to learn<br>
relevant technology and how the one could be used on Fedora.<br>
And may be not only on Fedora.<br>
<blockquote cite="mid:55B5B684.2020304@redhat.com" type="cite">
<pre wrap="">
That last one wouldn't be a pointer to any DA Assistants, but rather a
pointer to resources like choosealicence.com, and a review of some of
the available project hosting options (most notably GitLab, GitHub,
BitBucket and FedoraHosted)
Regards,
Nick.
P.S. A note regarding the Raspberry Pi: I think this is a good example
of a case where cross-distro development support is important, as we'd
like to make it easy for folks to develop for the Raspberry Pi on Fedora
while targeting both the default Raspbian image and the Fedora Pi remix,
rather than only supporting developing for the latter.
</pre>
</blockquote>
This is what is really currently missing on Fedora.<br>
If I want to use Raspberry Pi or Android then how to do it?<br>
<br>
It could be a big part on developer.fp.org.<br>
If I look on developer.ubuntu.com then I can see that there are some
tutorials about mobile<br>
experiences.<br>
Why we do not have it on Fedora. Hmm big goal for portal.<br>
<br>
I wrote an article [1] how to use android together with DA. But it
is in czech:(.<br>
I should write this article and paste them to livejournal
definitely. But time is against me;)<br>
I need at least 28 hours per day. Or not to sleep:)<br>
<br>
GitHub repo with this asssistant is here [2].<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://fedora.cz/devassistant-jak-vyvijet-aplikace-pro-android-na-fedore/">http://fedora.cz/devassistant-jak-vyvijet-aplikace-pro-android-na-fedore/</a><br>
[2] git clone
<a class="moz-txt-link-freetext" href="https://github.com/phracek/devassistant-assistants-nonfree.git">https://github.com/phracek/devassistant-assistants-nonfree.git</a>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<br>
<br>
<pre class="moz-signature" cols="72">--
Petr Hracek
Software Engineer
Developer Experience
Red Hat, Inc
Mob: +420777056169
email: <a class="moz-txt-link-abbreviated" href="mailto:phracek@redhat.com">phracek@redhat.com</a></pre>
</body>
</html>