How many are for NS ?? how many applies to NS ? Should I spend a few weeks months to read some of them before I can begin?
Steph give us the steps to be able to start… all the info outside Steph’s post must be considered prerequisites that everyone must comply to, full stop.
What information I need ? Do I know this information ? What to look for to be able to begin ? What kind of information should i be searching for ?
anyone, even if with a small experience (but with an active interest in being involved) can setup a dev invironment in minutes, maybe hours… it’s not a matter of skills but of willness and interests.
What experience ? If i do not have experience but i have interest, what should i do ?
This kind of approach is very negative.
Basically you are saying : Go learn Linux. Go learn C/C++, perl, PHP etc, go learn linux system administration, get yourself some programming skills, go learn some debugging… and after that come here to learn by Trial & Error what I don’t want to share with you, because i do not feel like you are worthy enough to be teached and you must discover yourself.
So in this regard, trust me that you will not have many (even at all) new devs or tweakers…
Before you know how to do a surgery you must be instructed how! You do not investigate on the patient by opening him up and going like “What does this little organ is… let’s chomp a little from here and see what happens”
tha’s all you really need…
if you don’t know what’s a virtual machine, how to install a package or run a CLI command, you definitely don’t need a dev environment.
documenting how to setup a vm, to install a package or run a CLI command is out of this community scope.
When I start this thread, It what to point one or two things that lack here.
The lack of accessibility to the information.
And to make something.
Here, to do something, the gui must be really motivate, without this, he can’t go ahead.
Yes, the doc exsit, but it’s not accessible, it’s hidden, or it’s in another site.
Yes, the doc exist, but perhaps it lack another intermediate doc to make things easier
And when the gui, like Ctek is motivate, there’s other gui to dismotivate, to said it’s useless.
Really bad day
We are here for asking questions and debating, and I always - always must say thank you for your time and effort.
If we want to make something, just start to do it. I’m with you, how can I help?
Information and howtos are not enough?
Can we try to gather as information as possible and start writing down howtos, TOGHETER?
Remind for everyone “Stonewalling communication” doesn’t help anyone. Be Agreeable, Even When You Disagree and improve always the conversation.
I think we need some sections for a good developer HOWTO:
pre-requisites
modifying a package
fixing bugs
create a new package
create a new UI panel
Pre-requisites
a working nethserver installation
a github account
First step - add developer environment
create a user from server-manager (i.e. filippo)
yum install nethserver-mock
grant developer permissions to filippo
usermod -a -G mock filippo
From here we could/should explain how to fork on github, clone a repo, make a pull request. But I think we can link an already written guide we could find on the web.
Maybe we could record a video tutorial and upload it to youtube.
I started programming when I was 12 year old till when I was 34 then I quit programming to do full time system administration (some times during life we must take some bad decision).
So I well understand @giacomo@stephdl as well as @jim and @ctek so I think we can do something togheter.
What do you think about a (yes an other one) NethServer for dummies programming guide?
Maybe we can pick a better title…
We can use howto also but IMHO they are better to explain how to set the environment but we need a guide to explain some programming concepts.
Honestly I would be happy to start back programming I would like to do my own “hello world!” program inside NethServer GUI
I think we can start following Filippo’s list exploding/developing every single point.
3 Likes
alefattorini
(Alessio Fattorini)
Split this topic
29
I’m proud to announce that I have created my github account, fork my first package and set up my local developing environment, I can say that practically
I have done nothing
First of all thank to @Ctek@filippo_carletti@stephdl for the howto, I made some corrections to wrong names or to improve legibility.
Now a question: which is the next suggested step?
Stephan in some post wrote that before start writing code he spent one year to read code of others before wite a fix, I’m agree with him but I would like to know a little more.
I think that this can help to expand the howto or (better) making a second chapter.
could you share any startup suggestions for learning devs?
keep it up mate!