Possibility of changing "Indie Python" project's name #8
Replies: 5 comments 15 replies
-
Just an additional consideration: As y'all know, with Nodezator surpassing 1K stars recently, the Indie Python project is getting even more visibility and our slow but constant growth rate is speeding up a little, which is great! That's why I thought that would be the perfect opportunity to rethink the name of the project, as the project and its software (mainly Nodezator), should go viral/get more views more often from now on. Since we are still relatively small, though, the change wouldn't affect us much if we make it this early, but now is a crucial time for that. |
Beta Was this translation helpful? Give feedback.
-
Hey Kennedy, good to read some news!! The first thing that came to my mind was "Indie go blue" (for the gilberto gil song) but you want to remove a language name, and i added "go" to the mix XD hahaha. Well i just wanted to say hi i guess. (y) Waiting to hear some more stuff about the new APP project. |
Beta Was this translation helpful? Give feedback.
-
Hello, everyone, Some of you may not know, but I actually learned a bit of PHP and Javascript in the past. I even make a primitive but functional CMS system in PHP for a personal website I had back then. I've also studied a bit of Rust and Haskell in the past couple of years and recently got back to my Haskell studies for the sake of learning about different type systems and as a result better understand the kind of typing tooling that projects like mypy bring to the Python ecosystem. This only served to stoke even more the fires of excitement and passion for techs/langs in general and my desire to make the Indie Python project even more inviting to users of other techs/langs. I even discussed this in more detail today in a reply to Mr. Alexander in another discussion. Here it is for your convenience:
I think all those words do a good job of summarizing the reasons behind changing the name of the project. With this, I'd like to proceed with the idea, and in fact change the name of the project starting in April. So far, no one expressly rejected the idea. At most, Mr. Alexander expressed that perhaps we should waint until a non-Python-based project was actually introduced before making the change. Not an unwise idea actually, but the truth is that, given all the work that goes into making a domain place first in search engines and for the name of the project to stick in people's minds, I'd like to make the change as soon as possible. Specially now that Nodezator is starting to get more views/visits/users, it is the perfect opportunity to change the name of its parent project and make it more widely known. In addition to that, in April I have to renew the That's why, if no one is against the idea, I'd like to set in motion the process to change the name of the Indie Python project. Please, if someone still has concerns or is against this, please, let us know here. For now, this is how this process will go:
Thank you for your attention once more. As always, all feedback is appreciated. Nothing in this project is set in stone and we are always open to dialogue and to change our course of action. Next I'll post a few suggestions I gathered on pygame/pygame-ce discord's server. |
Beta Was this translation helpful? Give feedback.
-
Here are a few suggestions I gathered on pygame/pygame-ce discord's server (the other ones were good names but were taken already):
|
Beta Was this translation helpful? Give feedback.
-
Call to everyone who gave feedback here: the pool is on: What will be the new name of the Indie Python project? @00-0o Thank you all for your feedback and suggestions. If a suggestion made here wasn't considered, it is because it didn't have a .com domain available or another project using it already exists. |
Beta Was this translation helpful? Give feedback.
-
Hello, everyone,
This is something on which I didn't decide yet, and even if I end up doing it, I'd only act on it on March/April (that is, changing the names/urls of our channels/profiles).
The change
The proposed change consists in replacing the "Python" portion of the "Indie Python" project's name for a more general term. That is, instead of "IndiePython" or "Indie Python", we'd use
Indie[________]
(a single word) orIndie [________]
, where the[________]
would be a more general term.This way the name of the project wouldn't limit us to using a single programming language. The new term may even be something more abstract or meta, to give us even more flexibility without compromising our identity, which will still remain centered around the independent development/production of open-source software and related content.
The exact term used will be chosen at my own discretion, since I must give it careful consideration and examination regarding additional things like the available domain and URLs in social media and other online services. However, I intend to disclose the final name to patrons of the project, to gather their feedback before ultimately deciding on it.
The reason
Programming languages and other technologies are tools. Each are great for some purposes and not so great for others.
Several open-source communities exist around specific programming languages and technologies, but even among their members there are people who use others langs/techs as well, or use that specific lang/tech in conjunction with other langs/techs.
Both in the Indie Python community and in the pygame-ce community I know people who use several langs/techs for work or side projects. C/C++, F#, Haskell. I myself started learning a bit of Rust and Haskell awhile ago, but also know a bit of PHP and a decent amount of Javascript.
Of course, everyone has their favorite languages/technologies, and loving/liking them is fine. But the contrary seems excessive, that is, hating a lang/tech or deciding to never use it is nonsensical and unscientific. At the very least, a lang/tech you don't like may offer you a competitive edge when used in conjunction with your main lang/tech for a specific problem. Who knows?
I don't know the origin of the expression/idea, but in some programmer circles here in Brazil people say that a developer wearing a shirt with the logo of a favorite programming language is like a civil engineer wearing a shirt with a wrench or a brick. Civil engineers don't fight among themselves over whether to use cement or plaster. Rather, they use both, depending on several factors, like the project itself, the purpose, etc.
Obviously, there's nothing wrong in using and promoting your favorite language, including the usage of related apparel. The point is that, when it comes to practice, we must not close our eyes to the benefits of other languages and technologies.
Implications
For the foreseeable future, that is, the next few years, this possible change (remember, I didn't decide on it yet) wouldn't change anything.
I love Python and intend to work with it for the rest of my life. It is also within the goal of the project to make and release games and I intend to keep using mainly pygame-ce for them.
However, making and releasing apps and games in other languages as well will greatly enrich the project. This will be possible because that will allow exchange of ideas with an even greater pool of minds from other open-source communities associated with different programming languages and technologies.
Even though bigger projects using other languages/technologies would only be included in a few years, starting from now, from time to time I might also release small utilities/minigames made in other languages as a way to help promote such exchange earlier.
Regardless of all that, I still intend to invest the majority of my time and effort in Python-based software projects. So the essence of the project would remain the same. We'd still be an indie Python project, but also one that is more open to other languages and technologies as well.
A more general/abstract term would also allow us to launch more ambitious projects in the future once we have more funding and a larger community, things like robotics, automation and other scientific related stuff. But that's for a good amount of years into the future.
As always, all feedback is appreciated!
Beta Was this translation helpful? Give feedback.
All reactions