Our Goals

[sadasant]

Here we'll set up the goals for this community. In this first section, we'll have our agreed upon goals, and in the subsequent comments we'll discuss about them.

Our Goal

Our curent agreed upon goal is:

Collect the greatest minds to cultivate new ideas and harvest high-quality content for the tech industry'

(Coined by @stefanmaric 🎉)

How we want to achieve this

We want to achieve this by:

• Publishing tutorials.
• Becomimg a free and open organization
• Publishing a release in a periodic manner.
• Reaching as many people as possible.

(Summarized by @guerrerocarlos 🎉)

What benefits do you get by contributing?

This might be better placed somewhere else, but in the mean time:

If you're an author

If you're an author you might want people to review your work, or a well known platform of publication, or to polish your ideas with other experts in the area. At the beginning, we'll have fairly limited resources, but we're all professionals so far, so the people involved can offer feedback that is not only well intended, but that will probably be valuable for the author. Some authors, for example, might not have enough time to deliver their full article, so other people in the community can help them develop it. Just like how it happens with OpenSource, doing something collaborative and open means that if something manages to grab the attention of people, it will likely get a lot of contributions, which I'm particularly really excited to see happening.

So, benefits for writers:

• Reviewers. Just like traditional editors, they give feedback about structure and intention to help the goals of the article.
• Help. If the author is a great software developer, but not as good as writing a meaningful article or documentation, their contributions in code might be rewarded with people helping them write content around them, or even other forms of contributions, like traditional code reviews and maybe even unit tests, it really depends on how attractive the idea is.
• A centralized medium. Just like a long running magazine, the total accumulated value of what's published can only increase over time (even if so slightly).
• Tools that empower everyone involved. Any tool developed for this community will benefit every author.

If you're not an author

If you don't have anything specific to contribute, you can help others to deliver their contents, this means:

• Getting to talk about interesting topics with content creators.
• Learning about the details of what will be shared from the inception of the contribution.
• Discuss with the community the details of a given contribution.
• Learn and enjoy the experience of working with others towards the goal of sharing a great idea.
• Maybe help as an organizer, it's not just about content, if you want to push for something to happen with the community, people will be able to do it. I'll talk about this at the end.

We are all content consumers at some extent. Caring consumers tend to communicate with the content creators. A collaborative medium might take this to the next degree of participation, when if someone doesn't agree with a contribution they can just fork it, or maybe you just have a doubt about a specific line while the author has a pull request as work in progress, this question could be responded by the author or other members of the community, and getting to know about early feedback might help the author address this from an early stage, perhaps it was a typo, or something that wasn't clear enough, or just the result of curiosity, which could be an early form of validation for the author.

If someone besides the original content creator contributes, specially if they commit to their branch (for example, if a pull request gets merged), the contributors instantly become co-creators (since ownership in git is about who makes the commits).

---

Back to organizers. Since it's a collaborative environment, less participative people will be following the guidelines of the most participative of us. However, discussions (just like this) can make us leap into another direction. This might sound scary, but it will be the only reason we will be able to release anything. This will only work if people manages to push for this to happen! The organizers that will emerge will have their own interests on doing so. My specific interests are about helping others release content since I feel it's a way for me to delegate this desire I have to write tutorials. Other interests include to see social experiments like this happen. From experience, once these efforts begin moving forward, further incentives will grow out of this community. If we get to the point of having constant releases, workshops will probably start to happen. Maybe meetings across the globe, which I'm really interested in doing since I miss my friends :)

Let us know if you want to contribute with this!

[sadasant]

Here are some goals that I'm thinking about:

1. Our main goal is to publish tutorials and other relevant content for people interested in technical topics.
2. For that, we want to become a free and open organization where people collaborate on building these contents.
3. Ideally, we would publish a release in a periodic manner. This periodicity ultimately depends on the production capacity of the group, so for starters we can set a relaxed deadline of three months.
4. The contents we build must reach as many people as possible, so we will need automated tools of distribution.

[sadasant]

An even more meta point of view is based on my belief system: I believe that productive people can self organize over a common goal to produce amazing content benefitting everyone involved, and attracting more brilliant people towards this goal.

Let me give you some background.

Years ago, I started a team at the university with the goal of publishing tutorials. This team used to release a tutorial per week, per person. We grew from 3 to 7 people, then to a hundred. We then switched to build technical events in the university we attended, where we would invite senior profiles from nearby towns and states to deliver free talks to students. We also built study groups around these topics. Then we moved to developing regional technical events. From that experience, we obtained job opportunities, business opportunities and notoriety with the regional media. All of this happened over the course of a year. Nobody was paid, and we all had a lot of fun. The core people from that team became close friends afterwards. At the end, we all had to move out of our country, but we haven't given up on the idea, we constantly go back to discuss about re-building this team. Here, I'm trying to make it happen.

So, again with the belief system: I believe this all happened because we managed to stay focused on a common goal, and we organized ourselves organically. If some of us push towards this idea, I believe we might be able to develop a new organization across the globe.

Also, I'm just trying to be the seed of the effort here. In consistency with our previous experiences, if someone happens to be more successful than me on making this grow and maintaining it, it's theirs, and personally I'll be fine as soon as people can still contribute afterwards.

[guerrerocarlos]

• Publish tutorials.
• Become a free and open organization
• Publish a release in a periodic manner.
• Reach as many people as possible.

That is a great list of activities, but what is the goal of these activities.

[sadasant]

The goal of these activities can vary depending on the contributions that can be made,

If you're an author

If you're an author you might want people to review your work, or a well known platform of publication, or to polish your ideas with other experts in the area. At the beginning, we'll have fairly limited resources, but we're all professionals so far, so the people involved can offer feedback that is not only well intended, but that will probably be valuable for the author. Some authors, for example, might not have enough time to deliver their full article, so other people in the community can help them develop it. Just like how it happens with OpenSource, doing something collaborative and open means that if something manages to grab the attention of people, it will likely get a lot of contributions, which I'm particularly really excited to see happening.

So, benefits for writers:

• Reviewers. Just like traditional editors, they give feedback about structure and intention to help the goals of the article.
• Help. If the author is a great software developer, but not as good as writing a meaningful article or documentation, their contributions in code might be rewarded with people helping them write content around them, or even other forms of contributions, like traditional code reviews and maybe even unit tests, it really depends on how attractive the idea is.
• A centralized medium. Just like a long running magazine, the total accumulated value of what's published can only increase over time (even if so slightly).
• Tools that empower everyone involved. Any tool developed for this community will benefit every author.

If you're not an author

If you don't have anything specific to contribute, you can help others to deliver their contents, this means:

• Getting to talk about interesting topics with content creators.
• Learning about the details of what will be shared from the inception of the contribution.
• Discuss with the community the details of a given contribution.
• Learn and enjoy the experience of working with others towards the goal of sharing a great idea.
• Maybe help as an organizer, it's not just about content, if you want to push for something to happen with the community, people will be able to do it. I'll talk about this at the end.

We are all content consumers at some extent. Caring consumers tend to communicate with the content creators. A collaborative medium might take this to the next degree of participation, when if someone doesn't agree with a contribution they can just fork it, or maybe you just have a doubt about a specific line while the author has a pull request as work in progress, this question could be responded by the author or other members of the community, and getting to know about early feedback might help the author address this from an early stage, perhaps it was a typo, or something that wasn't clear enough, or just the result of curiosity, which could be an early form of validation for the author.

If someone besides the original content creator contributes, specially if they commit to their branch (for example, if a pull request gets merged), the contributors instantly become co-creators (since ownership in git is about who makes the commits).

---

Back to organizers. Since it's a collaborative environment, less participative people will be following the guidelines of the most participative of us. However, discussions (just like this) can make us leap into another direction. This might sound scary, but it will be the only reason we will be able to release anything. This will only work if people manages to push for this to happen! The organizers that will emerge will have their own interests on doing so. My specific interests are about helping others release content since I feel it's a way for me to delegate this desire I have to write tutorials. Other interests include to see social experiments like this happen. From experience, once these efforts begin moving forward, further incentives will grow out of this community. If we get to the point of having constant releases, workshops will probably start to happen. Maybe meetings across the globe, which I'm really interested in doing since I miss my friends :)

---

These are just a few I can think about right now, let me know if you see more benefits.
What would excite you about a community like this?

[sadasant]

@guerrerocarlos Am I missing the point? Is that what you meant when you said "the goals of these activities"? I'm guessing the question was about why would people want to do any of this, that's why I answered like that. I can provide a different answer, let me know if you want something else.

[guerrerocarlos]

I think you have a very good idea of all the Objectives and Goals, I'm am just trying to throw light and avoid one of the main problems of any organization.

On any organization/community/group all the members should have very clear what is it all about.

These are two test to see if you really have it clear:

• Try to explain to somebody who doesn't know anything about it, under 15 seconds, and see if that person understands everything.
• Try to write it in a T-shirt.

[sadasant]

Uuh I want a T-Shirt!!!!

[sadasant]

Let's do that exercise, here's an attempt:

T E C N O Y U C A S
===================
OpenSource Magazine
Quality IT Content
✯✯ For  Everyone ✯✯

Gimme feedback :)

[guerrerocarlos]

Good approach, that is what you can provide to a customer/client of tecnoyucas.

The same you could do like:

C O C A C O L A
============
 Water and Sugar
 Addictive Chemicals
** For Everyone **

Do you think that is the Goal of Coca-Cola?

[sadasant]

@guerrerocarlos so, using CocaCola,

according to the internet, CocaCola's mission is:

To refresh the world in mind, body and spirit. To inspire moments of optimism and happiness through our brands and actions.

So, TecnoYucas's mission would be: To communicate quality technical content to the world, to learn together and organize ourselves freely, and to congregate the greatest minds available.

🤔 thoughts?

[guerrerocarlos]

I would add something to make CocaCola's mission more accurate:

"To refresh the world in mind, body and spirit. To inspire moments of optimism and happiness through our brands and actions, earning millions of dollars while doing it, thanks to the addictive components of the product"

I think we are getting closer :)

[sadasant]

@guerrerocarlos haha!
About the last approach, I'm getting feedback that it's too long, but I'm not sure how to shorten it :/

[guerrerocarlos]

From your TecnoYucas's mission I could extract specific objectives:

Congregate the greatest minds available to generate quality tech content and share it with the world, learn as much as possible in the process.

And synthesize it even further:

Rise the quality bar in the tech content industry.

[sadasant]

@guerrerocarlos Harvest quality content for the tech industry 🤔 matches with the whole yuca thing. Any idea with harvest ? or related? :D

[sadasant]

I really like rise the quality bar but made me think of rice and now I want something that resonates with yuca 🤔 thoughts?

[stefanmaric]

And maybe something with "Cultivate new ideas".

[sadasant]

cultivate!!! Also, the name is open for changes. We might want to keep the yuca thing, but tecno sounds like we're DJs

[stefanmaric]

Maybe like Collect the greatest minds to cultivate new ideas and harvest high-quality content for the tech industry.

[stefanmaric]

collect/gather/group

[stefanmaric]

Looking for some word that resonates with agro jargon.

[aitbw]

Just a small clarification, @sadasant: techno is the correct term for DJs

Maybe like Collect the greatest minds to cultivate new ideas and harvest high-quality content for the tech industry.

+1 for that, @stefanmaric

Also, +1 to gather —I think that's the one that fits the best

[sadasant]

I updated the description of this issue 🤗