I think there may be some crossed communications that I’d hate to see spiral out of hand…
I understand dt’s concern about having an active maintainer for a win build, vs. a packager. From what I understand they’d like to have someone actively maintaining a win version and able to contribute to that maintenance.
I can understand that part of the problem is the worry that someone will build dt, get a bunch of windows users on board (and all the associated bad things that the devs are worried about - more on that shortly), and then possibly leave or stop maintaining the build. Leaving many angry users hanging and possibly flooding any support channels they have…
I think the general perception of the last post was that the only thing lacking for a proper win port was a developer willing to be a maintainer (more on that in a sec).
So I guess, the questions are:
- Will dt support a win port at all?
- If yes, then can the dt team clarify exactly what their expectations of what a proper maintainer would be in their expectations?
This way, assuming dt is ok with a win port at all, it’s well understood ahead of time what is expected from someone willing to step up (avoiding any misunderstandings or unpleasantness).
About those windows users…
I know there’s some concern generally about the quality of user in terms of project feedback and bug-reporting, but I’d hazard a guess that early on the people using a win dt would most likely be more tech savvy than an average win user? Hopefully this could mean that more quality bug reporting and issues could be expected at a time when the port would be most fragile and benefit from better quality reporting (early).