You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What do you suggest? If you want a Grassmann.jl community too, then let me know how or if you want to get involved in making it happen, I feel like I'm jumping around by myself in a 1 person community -- despite having a big following.
As mentioned in #108 and #102 discussions, Grassmann.jl is well on its way to reaching v1.0 maturity... the v0.9 release cycle leading up to v1.0 is intended for community feedback ... as the core design has been completed. Feedback is not needed, but it's open source.
Your help is not needed for a v1.0 release, but anyone is welcome to get involved in finalizing Grassmann.jl to a v1.0 release.
If there are people who want to form a Grassmann.jl based community, now is the time to get involved in any way whatsoever.
I can single-handedly alone create and design Grassmann.jl into existence ... but YOU are the ones who have to engage in wanting to form community if you want to be involved.
I don't have an official discussion forum of my own at this time because I did not want to expend my energy on website design ... but if there is demand and community engagement, who knows what kind of Grassmann.jl community we can form.
There are a lot of cool features which aren't documented yet ... you have to engage with me to find out about them ... or wait until I get around to documenting those features and you discovering them. Contributors are certainly welcome to ask me questions and then add what they learn to the documentation too.
There are a lot of ways people could potentially get involved, it's really up to your imagination. However, what I don't like at all is copy cat projects trying to imitate my project ... that is not cool. Use Grassmann.jl to create something new, don't try to imitate me.
It's up to you, the potential community to get involved and engage ... I'm just out here by myself doing my thing.
The text was updated successfully, but these errors were encountered:
What do you suggest? If you want a Grassmann.jl community too, then let me know how or if you want to get involved in making it happen, I feel like I'm jumping around by myself in a 1 person community -- despite having a big following.
As mentioned in #108 and #102 discussions, Grassmann.jl is well on its way to reaching v1.0 maturity... the v0.9 release cycle leading up to v1.0 is intended for community feedback ... as the core design has been completed. Feedback is not needed, but it's open source.
Your help is not needed for a v1.0 release, but anyone is welcome to get involved in finalizing Grassmann.jl to a v1.0 release.
If there are people who want to form a Grassmann.jl based community, now is the time to get involved in any way whatsoever.
I can single-handedly alone create and design Grassmann.jl into existence ... but YOU are the ones who have to engage in wanting to form community if you want to be involved.
I don't have an official discussion forum of my own at this time because I did not want to expend my energy on website design ... but if there is demand and community engagement, who knows what kind of Grassmann.jl community we can form.
There are a lot of cool features which aren't documented yet ... you have to engage with me to find out about them ... or wait until I get around to documenting those features and you discovering them. Contributors are certainly welcome to ask me questions and then add what they learn to the documentation too.
There are a lot of ways people could potentially get involved, it's really up to your imagination. However, what I don't like at all is copy cat projects trying to imitate my project ... that is not cool. Use Grassmann.jl to create something new, don't try to imitate me.
It's up to you, the potential community to get involved and engage ... I'm just out here by myself doing my thing.
The text was updated successfully, but these errors were encountered: