error in tutorial
Johan Vos
johan.vos at gluonhq.com
Sat Dec 28 10:53:29 UTC 2019
Hi Ty,
Since I have absolutely no idea what you are talking about, I have a few
questions:
1. "... push changes to the repo..."? -> It would help giving a bit context
instead of talking about "the repo". Since this is the openjfx-dev list,
chances are high you're talking about the JavaFX repository at
https://github.com/openjdk/jfx. In that case, please read the README and
CONTRIBUTING files there for advice on how to propose/make changes (note
that this will probably take longer than 1 minute, as we have strong
quality checks in place). If you talk about a different "repo", please
follow the explicit or implicit rules on that repo(sitory). For example, if
you talk about https://github.com/openjfx/openjfx-docs , please create an
issue and file a PR, and work with the community to get it accepted. (note
that in this case, this should not be discussed on the openjfx-dev list
(note the *dev*)).
2. You refer to informal or formal talks you had, but it is totally unclear
to me who you talked to about what. Frankly, we spent lots of time moving
all code and as much as possible the documentation to github, so we can
easily track discussions. (for JavaFX bugs, we use JBS, so that can be
discussed there) If someone said "it’s the way we’ve always done it”"
please refer to the issue where your request has been made and subsequently
rejected, so I can have a look at the context,
3. Can you write a few words about what the word "Community" means to you?
Many people in the JavaFX Ecosystem spent tons of spare time in making the
JavaFX "Community" a friendly place. I'm interested in your opinion about
that word. To give a few options, does it mean
A: I insult people and companies, use words like "smoking shrooms" and
"stubborn" and I expect everything I think about to be fixed magically
(since I suppose the volunteers have no life apart from doing what I want
them to do)
B: I friendly discuss issues and opportunities with fellow community
members, where I respect other opinions, keep discussions polite and
technical.
C: somewhere between A and B?
- Johan
On Sat, Dec 28, 2019 at 12:11 AM Ty Young <youngty1997 at gmail.com> wrote:
>
> On 12/27/19 4:40 PM, John-Val Rose wrote:
> > Ty,
> >
> > If it’s so easy to fix then why don’t you just fix it?
>
>
> I don't exactly have the ability to directly push changes to the repo...
>
>
> >
> > John-Val
> >
> >> On 28 Dec 2019, at 09:14, Ty Young <youngty1997 at gmail.com> wrote:
> >>
> >>
> >>> On 12/27/19 4:19 AM, Johan Vos wrote:
> >>> Hi David,
> >>>
> >>> What tutorial are you talking about? If you refer to
> https://openjfx.io,
> >>> that is a community-initiative, developed at
> >>> https://github.com/openjfx/openjfx-docs .
> >>> So if you have issues and PR's, that is the place to submit and discuss
> >>> with the other contributors to that site.
> >>
> >> Only the Netbeans section has a warning telling you to delete src.zip.
> Neither Intellij nor Eclipse do.
> >>
> >>
> >> A user shouldn't have to do that anyway though! This could be easily
> fixed. Literally all you need to do is in this section:
> >>
> >>
> >> // Zip module sources for standalone SDK
> >> //
> >> // NOTE: the input is taken from the modular-sdk/modules_src dir
> >> // so that we don't have to duplicate the logic and create another
> >> // temporary directory. This is somewhat inelegant, since the
> bundled sdk
> >> // and the standalone sdk should be independent of one another,
> but seems
> >> // better than the alternatives.
> >> def zipSourceFilesTask =
> project.task("zipSourceFilesStandalone$t.capital", type: Zip, dependsOn:
> buildModulesTask) {
> >> destinationDir = file("${standaloneLibDir}")
> >> archiveName = standaloneSrcZipName
> >> includeEmptyDirs = false
> >> from modulesSrcDir
> >> include "**/*.java"
> >> }
> >>
> >>
> >> change:
>
More information about the openjfx-dev
mailing list