Jasonette's Future #23
Comments
|
I noticed and have been trying to track him down for the past week after not getting any response to a direct email. I won't jump to any conclusions except to say I believe the current situation is intentional. @gliechtenstein , if you're reading this and have truly given up on Jasonette and associated projects then please do a managed handover to someone else so that your much appreciated effort and the time others have invested doesn't go to waste. Nobody is going to hang you for having chosen one path (the correct one IMHO) only to decide that another path is better. However, it would be professional courtesy to provide an explanation and give people the ability make their own choice. Leaving things hanging is the worse possible option. |
|
@clsource could you re-open this issue and leave it for a while so others are aware of the situation? |
|
@clsource @dmoco Thank you for re-opening this issue, I agree with dmoco, it is important to let the issue open for a while so others can give their opinion. It is clear that is important to move forward with Jasonette because @gliechtenstein is not active and would be a waste to abandon this fantastic project and paradigm for mobile applications. However, Jasonette is maintained by the community and I think is important that not only one user should have access to everything but more members of the community should have the permissions as well. As is on the official site, Jasonette is free forever and open source forever and that must keep that way. So we must make sure that all the future contributions new versions etc to continue being free, open and that is possible if the community maintain it and not only a single member. That's my opinion and also I think that from now it should be on operation all the pieces that are possible to maintain at this moment such as GitHub contributions and not just to wait for a member to build a whole new site for Jasonette things must be addressed from now community members continue to build mobile apps and they need support. A new site should exist for and by the community and not only managed by a single member. This allows spending more time maintaining the project than if is only one member of the community. So as much as I agree with clsource I also think that more people must be involved in this turn around for Jasonette and the wellness of the whole community. |
|
@auniverse4 I personally do not mean to be the sole maintainer. I'm thinking a new organization with admin access because I cannot integrate anyone to the current organization. Obviously the community is the priority to avoid single point of failures like just one person having admin access. |
|
In case @gliechtenstein can read this issue. |
|
I currently forked all jasonette cell.js and st.js related repos in a new organization. As I told this organization will function as a mono repo style project with individual repos for readonly CI tasks. In the mean time here are the goals that this new organization will have: Current Jasonette, Cell.js, ST.js VersionMaintain SlackSlack could continue to be used as a chat platform. Maybe in the future replace it for https://keybase.io/ or similar. Release current dev versions as 1.0Current versions available in dev branch will be 1.0. Improve DocumentationPossible rewrite it from scratch following conventions in this video https://www.youtube.com/watch?v=azf6yzuJt54&feature=youtu.be Using gitbook or similar tool that could generate a pdf or epub. Divide it in the following sections:
Create a Jason.appReplicate the Jason app available in the Appstore and Playstore in an app that you could compile. In order to mitigate possible deletion from stores. Future Jasonette, Cell.js, ST.js VersionsDecouple Jasonette and Improve Code ReadabilityI believe Jasonette could be decoupled and the code improved in order to simplify development and foster new people contributions. Establish a predictable release cycleMaybe calendar versioning or something similar. Contribution GuidelinesDefine clear contribution workflow, tools and general guidelines. Improve debugging toolsIn order to ease development |
|
@clsource Some other useful repos to fork: Documentation: https://github.com/Jasonette/documentation Debug first steps: https://github.com/gliechtenstein/JasonConsoleAction-Android |
|
Hi, @clsource I hope you are doing well! hows it going with this project? is there anything I might be able to help you with? would be of great news to have ready the GitHub repos for Jasonette :) |
|
Ok here is it. But the building and other tasks are not automated. |
|
@clsource it looks great, well done is taking all the important things! I personally like it!, One question can we use an identity similar to what Ethan started to use for Jasonette? that way would be easier to be identified by the other communities, press, developers etc. just some minimalistic style similar to the cat style that Ethan was using { ˃̵̑ᴥ˂̵̑} can we ask the rest of the community? I know they aren't talking that much ... perhaps with good luck, we can collect some opinions about the identity thinking towards that there are people who have tested Jasonette in the past for tech reviews etc. |
|
As for the design and identity things I´m not an specialist in those areas. Maybe using the bird 🐦 emoji https://emojipedia.org/bird/ would do for a Choyke 👍 As the components inside Choyke you can see they maintained to be jasonette, cell and st. Choyke acts like a wrapper only. they will maintain their identity. |
|
Is not possible to keep the same identity as Jasonette and name? so that we can continue along the road with the contributions that already Ethan made I think is better if by legal terms we can keep it that way. Perhaps can choose some color set but the same identity if possible I think would be the best. |
|
It can´t be the same because they are different beasts. Choyke is the full package that includes cell.js st.js and jasonette. Jasonette is only android and ios. In the commits you can see that I maintained history, all Ethan contributions are there. Nothing was lost 👍 |
|
ok so I think everyone could be happy with this name 👍 |
|
That's a good one or maybe just Jason? sadly not too many people want to bring ideas, Jason is part of the whole framework you know it, even to start developing an app you have to do the $jason 👍 also makes reference to the mobile app to visualize the apps and so on ... |
|
Jason is the app in playstore and appstore. And is a name not available in github. Thanks for your suggestion but I believe Jasonelle is good enough 👍 . |
|
Another suggestion is Jasotron |
|
Thanks man. But I will stick with Jasonelle. Sounds soft and I just changed |
|
Yes is a good name 👍 I just wanted to offer some extra suggestions since our community members are not being very active..., lets do it Jasonelle! 😃 |
|
@clsource great job. Maybe life changes caused the absence of the lead. Hoping he's OK, just taking a long break. I have been wanting to do a project fork for a while. At least forking the iOS and Android repos will allow people do fixes, etc. I am happy to help maintain some things, triage bugs, etc. Note that a git fork does not appear to allow for issues to be created in the new repos, and I think that's important to do. |
|
@cpg Thanks, I hope @gliechtenstein is ok. Yes for the issues and prs it would be a manual process. For now I´m focused on creating the tools for a monorepo style project and ease fixes and bug hunting. You are more than welcome to collaborate in Jasonelle 👍 |
|
What is the motivation for having a "monorepo style project"? I think having a monorepo (whatever that means exactly) is not really a huge priority. Getting people to be able to build and fix some smaller issues would be a way to get things going one step at a time. What tools are you talking about for a monorepo? |
|
As I said earlier in this thread. The motivation for a monorepo is having a centralized stream of changes. A single place to tackle tasks, bugs and contributions. Eliminating the dispersion that currently is present. Contributing to such repo is easy. Just make some changes in the right directory. Thats all. I understand that some people would not be happy with such change in how the code is organized, but I really do not have the mental energy required to maintain several different repos with issues and other related stuff. I prefer keep it simple. One repo to store all code. On a side note I was enabled to reverse engineer the Jason App. Now you can use it and compile it yourself. https://github.com/jasonelle/jasonelle/tree/master/jasonette/examples/jasonapp 👍 |
|
@clsource thanks that is useful 👍 |
|
@clsource Would be great to reverse web Jasonette to run it in a local port, I have been seen it a bit, it seems to be running on nodeJS |
|
One step at at time |
|
No disrespect, but I have concluded that the monorepo is a genuinely bad idea, after
So, it's decisively a bad idea IMHO. I commend your whole takeover effort, however I would suggest you reconsider the idea. Having them as separate I think will entice more followers to keep this project alive without risking of burying them in a stream of updates they are not concerned about (incidentally, that is what following a whole organization can be used for!). |
|
I will try to address the issues and concerns you have. 1.- The barrage of emails could be easily solved by not subscribing to the main repo. You could subscribe to the repo you are interested in and receive only those notifications when changes are made. But i'm just starting. So if it something better came in the future it surely can be done and change it. 1- Accept pull requests to individual repos like cell, jasonette and st and merge them to the main repo when all the CI test succed. This could work I think so long I do not have to address issues and questions scattered everywhere. |
|
Maybe this diagram shows better what I have in mind.
|
|
I found this tool So now the main repo can easily fetch all changes from the other repos. I get a single place to coordinate and see the code. |
|
Nice move @clsource and I'm very happy to see this new commitment to keep this genius project alive, even a sad part probably happened to the founder, just a feeling from having spoken with him. It's not the kind of guy who will run after a hit and run. ;) |
|
Well mono repos are fine, Google and other big companies are using them now days. It could be as simple as, npm i -g meta and meta git commit -m 'commit to my area of interest'. But that is good if it makes it easier on your end :) |
|
All the code and newest version is at https://jasonelle.com |
Hello
Maybe some of you noticed that @gliechtenstein, Jasonette's creator is not active since June 9 2018. I personally believe he took some well deserved vacations and will come back some day.
In the mean time I have some ideas to keep Jasonette, Cell.js and ST.js alive. I currently have merge permissions to Jasonette repos but not Cell.js or ST.js repos.
I believe the best approach to manage and keep the flow is converting Jasonette Cell and ST to a mono repo style project. So one repo would be a "Meta Repo" wich will contain all the codes from jasonette android, ios, cell and st. Each technology would mantain its own repo but only as a way of executing CI tasks and keep the stars. In other words they will be read only. All the issues and pull requests would be in this meta repo. All the commits would flow downstream to each repo using some mono repo tools or github actions that could be created.
This mono repo style would improve the current situation with many issues and pull requests dispersed across many repos and I currently do not have the mental energy or the permissions required to tackle so many places at once.
Here is an article about the subject
https://medium.com/@patrickleet/mono-repo-or-multi-repo-why-choose-one-when-you-can-have-both-e9c77bd0c668
As for the domain name it could be renewed as a non owner process. I have a little conversation with namecheap and it can be done, but the problem is the dns. I have not access to the domains or servers that Ethan used. I can only renew the domain but not change the servers related to it. So there are two solutions. One is to renew the domain and hope the servers are still alive or two. Buy a new domain name. Waiting to the domain to expire and then buy it again is a risky move that could be done only if the timing is perfect or you are lucky, maybe using something like Namejet.com would help.
Slack can be keeped around because its free and do not require renewal, but I do not have admin access. For the other tools like jasonbase and the forums I currently do not have any way of keeping them alive if the servers are gone.
The final option is forking and create a new organization and domain name, with a new identity. Keep Jasonette alive but with an organization that I have full admin access. So I would now proceed to do that. And if Ethan comes back some day maybe we could merge the projects again. I currently do not have the same amount of time that Ethan had for Jasonette (He was fulltime Jasonette Cell and ST developer with no compensation for 2 years! ) but I surely have the love for the project needed to keep it going foward and alive.
When everything is setup I will update this issue 👍
Hope Ethan is well and come back soon. We really miss you @gliechtenstein .
Love to all ❤️
The text was updated successfully, but these errors were encountered: