This is another successful example from @GG_jr @dnutan @dz00te for our community 
3 Likes
This is a difficult one. It would be good to first identify who would like to enter this program.
On the āsupport sideā maybe a dedicated page/forum/ā¦ Could be created where tutors and volunteers meet and ask questions. Since this can and probably will be rather technical, a seperate section might be a good idea. Not to restrict access (as far as i am concerened it is open to anyone) but more to seperate the usual stuff from tbe really technicsl coding stuff.
I can be completely wrong here, but I am just following my gut feeling here.
There are some community coders that have shown their skills already. It would be great they stand up as tutors: @dz00te, @stephdl (all others, raise your hands!!)
There is absolutely a need for a good git(hub) guide to start with, since ns7 uses github as repository.
This github guide can be a good start.
As said, I am following my gut feeling here. I would really like to hear feedback on this. Add suggestions if you like.
I do find these developments in our community very exciting and hope this will be a major step towards maturity of the NetServer community.
clap clap for the guide @filippo_carletti, since a long time I didnāt read it.
@robb, the system you described is idealistic and must be the target to go, however the earth doesnāt turn in this direction.
Firstly because becoming a coder isnāt easy, and a lot of people wonāt do it well, of course they are good elsewhere. If you are a coder, go to github, read the source code, all the answers to your questions are there. Trust me, a coder knows it without me 
The second question to solve is how to do it sustainably, how to create, to maintain, to solve bugs all the time with the smile.
Recently I stopped all the work because an idiot asked me badly to solve a bug. Of course it is my mistake, but what I give is on my free time, beside my work and familyā¦and you know what, this guy is an Integratorā¦he earns money with my work 
Hope not here! Otherwise let me know his nameā¦ he should feel my whip! 
@dz00te I guess that bountysource is failed because of this. As we say āipse dixitā
3 Likes
One idea, surely too late for this year, however it could be bice for the next time.
1 Like
Sure. I thought about it many times in the past, provide good mentors and submit the application programs isnāt so simple tough
But it absolutely could (and probably would) generate a HUGE boost in code for NethServer. Think of all those extra modules we could addā¦ 
GSOC could be a great accelerator for NethServer, sadly there are many things to do before submitting a project and much more during/after the development.
Right now, we donāt have enough resources to follow such project 
But if anyone want to mentor a student, we can try to arrange something.
Iām fresh from the community leadership summit. Needless to say, I suddenly ask the attendees which strategies they adopt in order to involve more developers. Thatās what they suggested me:
- create junior issues. Easy things to do, maybe split from big tasks/issues. A junior issue needs to be deeply explained using high-level terminology so that a newcomer can easily jump in and start to make some tests.
- junior issue main features are: no urgent, no blocker, shouldnāt be fixed by the dev team.
- mentoring. Junior issue need to be the occasion to train junior devs, even if theyāre not so effective in terms of productivity. (mentoring costs more that getting the things done on your own)
- participate in GSOC and outreachy program. Again, it highly suggested to allocate some resources to follow these project, aiming to long-term results.
How can we start to identify and create these type of issues?
What are your thoughts? @dev_team @ambassadors_group
Edit: again I know, itās time-consuming but no pain no gain, folks!
6 Likes
We have created a new āJunior jobsā column inside GH project: https://github.com/orgs/NethServer/projects/1
Check it out!
4 Likes
This thread is still active, nice to write down my mind. Lastly I talked with a friend about the modules I made, around 26 modules yet. He was surprised, seeing the work, the time, the hardware I need.
When you do a āyum updateā, it is free for you, but I have a mirror that I pay 50ā¬ every month, I have a server at home to build rpm and test them, a laptop because often I code when Iām not at home.
And of course the electricity is free in France. I estimated the cost about 1000ā¬ per year, but I donāt talk about the time to do itā¦10, 20, 30 hours per weekā¦how much do you pay a developer in your country ?
The bounty was tried, but the amount is really low, giving 40$ for nethserver-fail2ban.
I can see my motivation decreases, because I have never reached a sustainable way for development. Do Iām the only guy able to pay, to code, to deliver for free a work that others can sell to their customers or their bosses.
Saying this is funny, but real !
Iām not depressive, I have had two little delights recently
- I have a paypal button, asking for donationā¦and I have had 50ā¬ lastly (first donation since 2014)
- I have had a nice PR from @dnutan ā¦nice to not be alone.
Iām in a big period of meditation to find some interests back for me, Iām not sure that I can continue a long time like thisā¦but my code will/should stay free !
4 Likes
Iām understand you feeling pensatif with the amount of buckā¦
And did you already think in a VPS for the dev structure?
1 Like
@stephdl,
50 euros per month seems to be expensive for a remote mirror (I am presuming by mirror, you mean a server with either ftp / sftp or http access and some sort of cronjob styled synchronization with the original distributions repositories).
Especially considering that I am spending approx 27euros (Ā£24) per three months for a VPS (iperweb.com)
1 Like
I use proxgroup for hosting , and their VPS offer are like this priceā¦
And you wll economize with electricityā¦ with backupā¦ with stress!
1 Like
No one is getting stephās pointā¦
1 Like
I feel you. From my point of view you have two ways:
-
Be paid by download. You close your repository and ask to be paid every installation. Just a few $ and itās scalable basing on how many installations NethServer has. It has cons: you need to setup an infrastructure and people canāt test/use the rpm before they paid for
-
You set a price for a module, basing on your estimate. Before develop something or after a POC. And until the amount is reached you donāt start the job
For example: urbackup for 7
We can advertise and publish it on BountySource and community members or companies are invited to pay the bounty to obtain the rpm
PROS and CONS
Following the first way you can produce more revenue, but you need an infrastructure and you donāt know how many downloads you will reach before.
Following the second way, you can obtain less revenue but itās secure and you will receive it in advanced. Furthermore, itās more community-compliant One requirement: put the right price based on your possible estimate so it can help you pay your bills.
Think about this, I am happy to help.
You have to be rewarded for your effort
3 Likes
@stephdl first of all thank you for your work, your effort and your code
i was thinking about this thread some time agoā¦ i think that it should be a topic of nethserver conference in September.
ofcourse i didnāt have a solution, sorry, so this is just thinking loudā¦
-
one possible solution should be something like the UCS app center https://www.univention.com/products/univention-app-center/
this require a major effort for devteam to integrate it , but i think in the mid-term it could be a win-win solution for both core devs and external devs. -
bountysource didnāt work very well. I think it could be practicable when there is one āmajor sponsorā (usually a commercial user) interested in a package and some other (usually private user) contribute with small amount. Also if sometime no all user know the package so at the first time are not interested and only when the package is available they discover the usefulness of the package, and this mean loss of contributors.
-
as @alefattorini said, a paid repo. but as reported the major cons is that no one can test package. A possible solution is to emulate the red hat/nethesis way: a public repo for community version and a paid repo for enterprise version. This means that all can evaluate the package, and in any case also for community version the āpaypal buttonā should be well visible at least in netheserver wiki for every single modules (this could be done right now)
-
stop coding an join the QA Team
3 Likes
Or nobodyā¦ or everybody!
The community is smalllā¦ Few return !
The Nethserverā¦ ( and SME) is relatively few adopted by Linux usersā¦
The Stheph dev structure is overpowered regarding the expecting returns!
Interesting POV, but wrong