Hacker News new | past | comments | ask | show | jobs | submit login
Cyclotron: A web application for constructing dashboards (cyclotron.io)
351 points by severine on Nov 29, 2016 | hide | past | web | favorite | 112 comments

I would like to share some thoughts on this based on experience of being a crusty old enterprise developer. The dashboard problem keeps coming back. I think the time might be finally coming for some dashboard framework to actually succeed.

A dashboard framework has been tried many many times. Here are some old ones just on the top of my head:

* Shindig aka OpenSocial aka Google Gadgets

* J2EE portlets

* OpenUSS

I'm not sure why Shindig aka Google Gadgets failed but one of the complaint we had on a product that I helped build that used Shindig is that business users did not want the complexity of customizing a dashboard. That is hard coded panels were good enough.

I guess just like many tech stuff (slack/irc, wiki) the timing and execution just wasn't right. I think now that might change given the plethora of devops, data driven biz, and generally improvement in tech awareness.

It would be nice if Cyclotron had some sort of spec (particularly language agnostic) but I guess that failed hard for the above.

For my own small company we use Kibana (the old one that doesn't require NodeJS), Grafana, and Jenkins.

Yes we use Jenkins as a dashboard. Jenkins is actually shockingly a good place for a dashboard because every time we build/deploy or kick off some kind of job we see the current status of stuff. I'm not sure why cloudbees hasn't taken advantage of this. I honestly think it is the best place to put devopsy like dashboards.

The other nice thing about Jenkins besides it actually kicking things off is the notification. IMO notification is almost more important and more useful than dashboards. The two should be not be far apart but for some reason in most systems they are.

I totally agree about combining notifications with the dashboard. I built up Godot2 [0] to solve this for myself. It can take any metric, including metadata, and stream to notifications via Slack, email, SMS, as well as the dash.

The incoming events have a spec, like Riemann, and is compatible with Graphite. Godot2 also has it's own mini query lang [1], which allows for easy selection of events for the dash, e.g.

  service =~ 'health/machine/disk/%' and status = 'ok'

[0]: https://github.com/nextorigin/godot2-dash

[1]: https://github.com/nextorigin/riemann-query-parser

I work in an industrial manufacturing plant. My Manager is always going on about dashboards almost every week I hear something like "I'd love to see this on a dashboard" (usually referring to something on an existing printed report). He has been saying this for years and no usable dashboards have ever materialized.

I think the biggest issue is no one in our organisation has a clear idea what a 'dashboard' is exactly and how people are supposed to use them.

For some people a dashboard is a static page that gets refreshed periodically. I.E. "Lets show the current line speed in big bold 48pt font size and auto-refresh the webpage every 15 seconds."

For other people a dashboard is something interactive (drill down, selectively trend values, modify trend scales on the fly etc).

So there has always been this tension between the two use cases and we always end up with these halfhearted things (usually built using some BI package like COGNOS) which are the worst of both worlds.

At the same time a dashboard has never really been in high demand. So I think people like my manager have really failed to articulate the value a dashboard would supply.

The most promising thing I have seen recently is "Coresight" by OSISOFT (we use their PI plant historian system pretty extensively). They gave a demo that integrated control system type information (Conveyor status's, Flow meter readings, Tank levels etc) with location derived GIS data to show realtime updating maps etc which I thought was pretty cool.

> For some people a dashboard is a static page that gets refreshed periodically. I.E. "Lets show the current line speed in big bold 48pt font size and auto-refresh the webpage every 15 seconds."

What do most people use for this kind of use case, assuming changing of the values needs to be scriptable?

Jenkins: the duct tape and WD40 of software automation.

I have seen people use it in some amazingly Rube Goldbergian ways for great success. It's a real credit to the project and the ecosystem.

Easy enough to 'just get the thing done', but as complex as you want it to be.


How do you deal with Grafana having no isolation? Do you deploy a new instance per client? Each user has full access to all datasources from what I've seen.

We use Grafana for our own internal usage (albeit we do have customer viewable analytics but it is proprietary hardcoded panes).

I suppose you are confused because of my mentioning building product based on shindig. That was a previous employment many moons ago. I now am a many hat wearing owner of a SaaS.

While I'm speaking of Grafana I find Kibana for more useful probably because we have a lower level of traffic than big boys but still produce an atrocious amount of logging. Logs are damn useful. In some ways metrics are actually a subset of event aggregation (ie logs) so I think Kibana is more useful at first.

You are mistaken. Grafana has RBAC and datasource isolation.

I wasnt entirely clear in my previous comment, grafana allowed clients to issue full queries against all datasources the user has access to. So if you have one datasource with metrics of all your users and want to give them access to dashboards that only display their own data, that is not secure.

Ah, ok. I had the same problem (from Graphite era) but splitting the datasources up was fairly painless.

Are there any nice Jenkins plugins for making a decent dashboard?

Sort of: https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View

Basically you create plugins and make sure they are compatible with the dashboard view plugin.

The nice thing about jenkins is the contributed plugin packaging system. I'm not sure how Cyclotron plans on doing that stuff or if it will ever.

How does this compare to something like Grafana? https://github.com/grafana/grafana

I like Grafana. I use Grafana. I've got Grafana open in another tab right now. For all that, Grafana ain't all that and a bag of chips.

Grafana is very hard to extend with new visualizations. It uses "flot", a JavaScript library that hasn't seen a commit in Github in 2 and a half years. The documentation is poor.

There is definitely a need for dashboard software that allows for more complex custom visualizations -- I'll be looking closely at this.

The latest versions of Grafana now have a pretty extensible plugin architecture, and the types of panels have been growing by the community at Grafana.net. We're even seeing some new contributions that use D3 instead of Flot, which is super exciting to me.

Full disclosure, I work for Grafana, but seemed relevant to mention.

I worked with Chart.js contributors to add real-time graphs, to use them as a replacement for Flot in Godot2-dash/Riemann-dash.

Here's examples of the final result [0], it's better than I could have hoped for.

[0]: http://playground.abysscorp.org/chartjs/livecharts/

I haven't run across a worse-documented or harder to wrangle JS charting library than Flot, ha...

Have you tried appenlight charting?

Hi, Cyclotron developer here. I think it's fair to say Cyclotron is a bit more open-ended in terms of what you can build, whereas Grafana dashboards are a bit more structured and tend to look more similar. While Cyclotron provides common widgets and dashboard functionality, it also makes it easy to add custom HTML, JavaScript, CSS, etc. This broadens the potential use cases quite a bit. The downside of being more open-ended is that it doesn't provide the same level of rich interactivity out of the box, which Grafana does.

Additionally, when Cyclotron started, it supported pulling data from a handful of different data sources, whereas Grafana was focused on Graphite. Grafana has definitely come a long way in the last year in this regard though.

Can I just take a moment, and I apologise up front for singling you out for this one, to say how much I hate comments like this, even more that they get upvoted.

There's always some arbitrary software mentioned that is often barely related even tangentially and expect someone else to reply with the info.

If you want to know how it differs, YOU look it up and if the outcome of that research is interesting enough YOU post it. Don't expect other people to do it for you, or worse, make it so that the creator of something that might not even be the one linking it feels like they have to justify why they open sourced something.

I disagree 100% with you. I love comments like GP. Any new tool should be considered in comparison to the other tools one might use for the same job.

Is Grafana "barely related even tangentially"? No it is quite related.

Have the creators of Cyclotron considered how it compares to existing tools? Probably, and they should come forward and be open about it.

Exactly. I need to understand what value this particular software brings to the table compared to the "competition" before I will invest any serious time into looking at it.

> Probably, and they should come forward and be open about it.

No software developer is obligated to do anything for any of us. It's on US to figure things out and share them as we see fit. Nobody cares if you are willing to invest serious time looking into it or not. Asking a leading question and linking to something most of us have already seen is pointless. Defending it when a good argument was presented is also pointless. I hazard these discourses are linked to age.

Stop presuming that just because you're familiar with something that it's no longer worth bringing up. I've never used any of these tools and value the discussions about them that questions like the thread starter's allow.

Further, there are always new people looking to learn and grow. They shouldn't be looked down upon simply because others got there first.

What makes you think the question was a leading question rather than a genuine one? There isn't enough there to definitively determine the intent in any case, so it's up to whoever responds to decide which way of reading the question they will respond to, and that's an opportunity for the larger software community and for the developers of the projects in question to nurture thier communities. Just because it doesn't have value to you doesn't mean it doesn't have value to others.

I find GP's kind of post and the discussions that often follow to be some of the best on HN, IMO.

To me, it's the spirit of your post that drives many away from software development. This holier-than-thou attitude of how dare someone ask a reasonable question of people who might be able to easily answer, or direct to an answer.

Someone asking a question like this isn't saying, "Hey, next person that comes by, do some research for me" it's saying "Would someone that has already done this research mind sharing their findings?"

Progress in knowledge base communities is driven primarily by building on existing knowledge. The more readily knowledge is shared, the faster progress will be. So having a culture where anyone seeking answers must redo the groundwork that has already been done by others in order to "earn" the answer is an impediment to progress within that community.

The poster above made a great question to the community. There is an amazing amount of value from the feedback that experienced users provide. Ive gotten a lot of value from people who post similar questions because others go out of their way to help. Ive discovered many a great software like this. The comment gives the OP the chance to compare pros and cons from a technical point of view. Its not a personal attack, but an invitation to discuss a software in technical terms.

I don't think this is fair criticism. Grafana is an exact competitor to this, and as the market leader, it's only natural to be the benchmark.

Well Grafana being pretty much the dominant dashboard tool for most users seems to make it the thing to compare against. I disagree with your thought as well. If I was to make a competitor to say Linux, it is up to me to tell people why it is better. Seems entirely reasonable to ask for seeing as how Grafana has support for an unbelievable amount of things and is quite battle tested for real ops and dev teams.

IMO this is totally backwards. A new product should justify why it's preferable to what's out there. Don't waste potential users' time making them research when you could just lay it out for them.

Well, I for one I'm with weego. The way I read it anyway, he's not against "How it compares" posts, he's against "How does it compare?" ones.

Quite frankly, if you want to know it takes five minutes to head over to the respective docs and get a rough idea, as I just did. If you're super-motivated you can even then share your conclusions and tell us "How does it compare: like this, this, and that" (which I won't).

But just shooting a question away like that is not helpful and comes across as lazy.

What about how if someone has read the docs and could answer the question would become motivated to write up what they think because they see someone is interested in knowing? Losing that opportunity for sharing knowledge is, in my mind, worse than having the question not appear at all.

And lazy? Since when is asking questions is lazy?

People are reading a lot of intent from what was a very plain and straightforward question. What I think would be valuable would be if someone shared why the mere presence of such questions is somehow detrimental to the point that they can't simply be ignored, which I don't think has yet been explained.

no I like these short posts too, even though with more info it will be more helpful. Providing related links is still useful, it took me less than one minute to check out quickly. Thanks.

I agree with you! This is how I found VueJS when someone made a similar, tangentially related post which was essentially, "Yea but I like VueJS much better for reason x". It exposed me to something I didn't know about.

Consider that a comment like OP's starts a conversation about this product and also shares a similar product with the community for more exposure. Sometimes, the creator of the product will even step in to expand on the topic.

It's not the most articulate way of starting the conversation but it is effective.

> If you want to know how it differs, YOU look it up and if the outcome of that research is interesting enough YOU post it

Would you read a scientific paper on well-established topic X if it omitted a comparison to related work?

X, here, being dashboards.

Most teams at Expedia use Grafana now. Cyclotron was built back before Grafana existed.


From a superficial perspective,

Grafana is

> Go 33.9% TypeScript 26.4% HTML 15.0% JavaScript 14.2% CSS 8.5% Shell 1.6% Other 0.4%

Cyclotron is

> CoffeeScript 45.1% JavaScript 30.5% HTML 15.4% CSS 8.9% Nginx 0.1%

Both are using Angular 1, installed via bower ([Grafana is on 1.5.8](https://github.com/grafana/grafana/blob/master/bower.json), [Cyclotron is on 1.4.9](https://github.com/ExpediaInceCommercePlatform/cyclotron/blo...)

I really like grafana

I love Atlasboard because it's simple and you can do anything, anything at all. The only limit is your imagination. Welcome to Atlasboard.

Seriously now I wonder how Cyclotron compares.

this one looks good and it uses postgres

> this one looks good and it uses postgres

Where did you see that it uses Postgres? I think it stores its data in json files.

I checked out node_modules and found postgres there but I have not looked into the src to see how it's hooked.

There is also Redash http://docs.redash.io/en/latest/ We are using it and it's awesome.

Redash is amazing. I used it for a little while on a retail analytics project. Arik, the lead developer and founder, is awesome and super responsive to emails.

I was hoping that this would be a maintained fork of http://dashing.io/

Well, there is the official fork - https://github.com/SmashingDashboard/smashing - Last commit 20th Nov 2016

Dashing was always my vibe. Good to see it's still being worked on.

Disclaimer: I work on Metabase.

Another open source option: Metabase http://www.metabase.com/

We support most SQL databases and a bunch of others, plus upcoming support for Google Analytics.

Why MongoDB for what is pretty much a front-end :( What's wrong with SQLite?

"The path of MongoDB is often the same: first the primary DB, then the configuration store, then it's finally removed" - (friend of mine)

Solving imaginary scaling issues at scale.


Expand. MongoDB is finally removed? Why?

I think the implication is that mongo is picked because it's "cool", and eventually everyone realises another tool does the job better

(e.g. regular sql database/redis/sqlite/etc)

More front-endy, see Dashing, now Smashing, a Sinatra based framework that lets you build beautiful dashboards.


You can store models in SQLite:


There seems to be a plethora of these open source dashboard builder systems.

I just want to pay for a hosted version that isn't going to be $1k monthly and require me to build "plugins" to do something that is akin to an API call.

Microsoft Power BI [0] is only $10 per user per month, while Amazon Quicksight [1] is $9 per user per month.

In the startup space, there is also Mode [2] which has reasonable starting pricing at $25 per user per month.

I've used all three, and my personal favorite is Power BI. They are all great though.

[0] https://powerbi.microsoft.com/en-us/pricing/?b=1

[1] https://quicksight.aws/pricing/

[2] https://about.modeanalytics.com/pricing/

I want it to be a $1K/m so they can stay in business and build a sustainable thing I won't have to replace. That's still way cheaper than spending 1/4th of an engineers time per year on an open source dashboard.

In a business/enterprise context, why not use Power BI?

>I just want to pay for a hosted version that isn't going to be $1k monthly and require me to build "plugins" to do something that is akin to an API call.

Sorry for a shameless plug, but you might check something that I built and launched today [1] as I felt exactly the same pain point.

[1] https://monique.io

Very cool. I'm going to take a closer look at this. Congrats on the launch!

InfluxDB + Grafana is a super easy combo to set up (two binaries, no dependencies) and it's very low maintenance once it's up. If you are looking for something that's both affordable and hassle free it's a pretty good alternative, even if self-hosted.

I've considered offering a hosted version of Godot2/Riemann+dash. What would be your main data sources? Would you pay $100/mo?

Librato. Unfortunately, their free offering has stopped, even though that was my main way of converting people into using them

getappenlight.com could be a solution it takes the data from logs (basicly json input) and allows you to plot charts from that data and generate alerts from that.

Looks like a hosted equivalent of GeckoBoard[0], which I have used successfully for uptime and key metric boards that are displayed in common room dedicated TV screens etc.

One key is getting decent render performance on low-spec hardware (i.e. a Rasberry Pi). Not something you usually think about when building/evaluating a web app, but those low-spec "boxes" crawl on most modern web-sites.

Yet there shouldn't be any reason why a dashboard couldn't be rendered on them!

I wonder how Cyclotron performs with it's JS heavy front-end on those types of dedicated dashboard devices?

[0] https://www.geckoboard.com/

Forgive my ignorance... what makes a dashboard different that a regular webapp?

A dashboard is a web app displaying aggregate data - usually on something like a digital signage display at a company's office - often includes 'vanity metrics' like web traffic data, Git commits, social media feeds, CI builds, etc.

To expand upon that, it's aggregating a variety of data sources, generally via disparate APIs, rather than creating its own database backed API.

So while most framework models are oriented around their own ORM, a dashboard is probably better off modeling a set of translators, and providing tools for adding new translators. Translators can take a random API, and convert into a normalized data type the rest of the framework can understand. And a good community will have a lot of these translators available.

Additionally, the dashboard framework can provide a variety of standard visualizations for the translators to send normalized data. Time series, histogram, pie chart, text, etc. And provide an intelligent layout engine for arranging a collection of these on a screen. Dashing, for example, allows a user to re-arrange dashlets.

tl;dr -- it _is_ a webapp, but the more limited scope allows for better tooling and your valuable engineers can focus the more productive uses of their time, like writing new visualizations or, more likely, new translators.

Anyone know Baidu's echarts? http://ecomfe.github.io/echarts/index-en.html

There is also https://mondash.org/, which is has a clever API that may be very useful in some cases.

Nice! Some quick feedback:

* I'd default to the "light" theme, especially if you're presenting it against dark background. It will highlight the content better. * You could use some whitespace between the widget titles and the content. The text is sliding into the graphs. * Might be nice to use more than two colors for the graph content, or at least make one of them different from black, which is also the color used used for the tables and titles.

This scared me a little bit. We've been doing a similar product https://vida.io. I think we've got a lot further with many components and dashboards, see https://vida.io/explore. At the same time, I'm pretty excited to see someone has similar vision about custom data visualizations.

To be honest I don't understand why should a dashboard framework need MongoDB to display widgets from external sources.

[shameless plug] We're also building an open-source dashboards framework https://github.com/kittoframework/kitto

I like how you can change the Cascading Style Sheets pretty much on the click of a button. I am a bit behind the time, but I do remember Square's Cube to be good for time-series.


Those can be embedded into dashboards

On a side note, any site like HN for data systems, BI, dashboards?

Edit. To be clear I mean forums where business intelligence, data science, dashboard folks hang out. I work with Tableau and they have a big community, I am looking for sites less tableau centric...

What do you mean exactly?

How is this different from potential alternatives like Geckoboard, Ducksboard and all those? Is it essentially not just another one?

This seems pretty cool. Though running it as an intrAnet app is unexpected.

Though in many corporate settings, that's where you'd expect to see it. Many externally facing dash frameworks require too many dependencies; this one went lighter in some ways b/c they assume that it's behind a wall and in a trusted environment.


"Can I Use Cyclotron to Host Dashboards on the Internet?

It is not recommended to deploy Cyclotron as-is in a public setting. Cyclotron was designed to be used in a corporate intranet environment, rather than for public dashboards. In addition, it's possible to create malicious dashboards using the extensibility features of Cyclotron. Allowing untrustworthy users to create dashboards is not recommended."

It requires mongodb to run, eeeewwww: http://www.cyclotron.io/faq.html#without-mongodb

Not something I'd trust as a primary datastore.

what about openmct. iirc it was a complete dashboarding tool.

Nice product

Thanks for project

I never understand why people choose MIT when they create something valuable and don't go for AGPL or GPL.

Looks good though :D

I use MIT because I want others to use my code. That's all I want for my code. It's a gift. MIT is user-friendly (read: less restrictive).

Because MIT is simpler? Because MIT doesn't require any specific license usage in the future?

Maybe they want people to actually use it.

Because Software like Wordpress, Drupal, Joomla, Typo3 and so on isn't used?

Pointing out that a lot of internet runs, in part, thanks to millions of lines of GPL code that people reuse and extend on a daily basis? Well, it isn't allowed, I'm afraid. It breaks the narrative that the GPL is old and busted garbage, you see, and we can't have that going on in these parts. Consider yourself persona non grata #1 with that attitude!

It's very simple. It would mean my soapbox wouldn't feel so tall when I speak, and that when I take other peoples code, I might, some day, actually have to give something back as a result. As opposed to just taking it, profiting off it (like ~80% of people who 'eschew' the GPL because they can't make as much money as possible off it) and never doing anything in return.

As I'm sure you can understand, those consequences would be utterly devastating. For me. I hope you can fully empathize with my plight, so we can reach a mutual understanding. Preferably in the form of you giving me things with no strings attached.

> As opposed to just taking it, profiting off it (like ~90% of people who 'eschew' the GPL because they can't make as much money as possible off it) and never doing anything in return.

This right here - though I would extend it to also mention those who take it, extend it, profit off of it, then next-to-never (and many times never) returning any of those changes back to the community.

If we're lucky, they contribute something else back (and those contributions are welcomed, mostly) - but never the changes which allowed them to grow and expand well beyond anyone's expectations. We all know who you are.

I understand the want to see my code used by "the big guys" (or the "up-and-comers" who become "the big guys"); it does look good on one's CV. At the same time, I also understand Stallman's reasonings and message; he has personal experiences which led to the creation of the GPL and his philosophy on software - and he has been around long enough to see how the corporate world really works when it comes to the lifecycle of software. From the birth of an application or system, to its use and adoption, to its death.

Sometimes, its the latter end-of-life phase that we seem to forget about. So often as developers we have to "re-invent the wheel" when had old proprietary software source code been released at EOL, a base to build something better would be in place. Unfortunately, then as now, software has been looked on as an "asset" to be traded and sold for profit, despite the fact that it also depreciates faster than a new car. Yet, like an old Vega, some desperately cling onto that old software hoping to profit "someday, you'll see!".

And in many cases, that source code, and even the binaries - suffers the ignoble fate of "bit rot", sitting in a warehouse on an old hard drive (if we're lucky - if not, it's on some old nearly unreadable 7-bit paper tape literally rotting away, in a format used by a computer system that hasn't been turned on - if one even exists and hasn't been scrapped for gold - in over 50 years).

Original symbolics LISP? Some of the code behind the Apollo program (heck, and that was government funded!)? Cray Research operating systems, compilers, libraries, etc - for the old Cray supercomputers? This list could be extended nearly forever.

The sad thing is, we have lost man-centuries of work in the form of software, due to want-of-profit and bit-rot - and Stallman knows this - we should all know this. Furthermore, even when the code does survive (in whatever form), inevitably, the systems that can run it do not (in general); in some cases, it has become impossible to run code written for certain machines because no examples of those machines, nor their designs (to create an emulator) exist any longer. All we can do is guess at what the program should do (assuming we have at least documentation of the mnemonics and opcodes for the machine language binary to reverse engineer - if you don't have that, nor the real hardware, the binary code might as well be noise).

Crazy enough - in some cases we have the machine and the software extant - but only one operating copy of that machine! For example, there's a company in Texas which uses an old IBM accounting machine to this day; it uses punched-cards for it's data input/output, plus it has a printer. It's "programs" are hard-wired plugboards. A computer history museum delegation has begged them to donate the system to a museum for preservation, as it is the last operating example of such a system. But the company has an attitude of "if it ain't broke, why fix it" - and you can't fault them for that. Even so, one day it will break, and likely whomever is in charge will decide to sell it for scrap rather than donate it (due to likely amount of precious metals in the machine) - and that machine, plus all of its programs - will be lost forever.

Heck - we treat our automobiles and automotive history with greater respect, and that has had arguably a much lesser impact over the last 100 years, than what computer technology has had over the last 20.

/end ranting (and book)

Because people these days want to use open source codes freely, without bothering with License. And people who open projects wants their project more widely used. GPL is too restrictive for new projects.

All the GPL says, at it's basic core, is that if you incorporate the source code of the software into your source code, you must provide a means for others to get a copy of that extended source code, and they must adhere by the GPL license as well.

In other words, if you GPL license your code, and someone else uses it, they need to "pass it on" - in other words, their payment to you (and the community) for using your code is for their changes to be passed back to you (and the community).

Code paid for with more code - imagine that.

The only restriction is against those who seek to profit (almost) exclusively off the source code, in perpetuity. They want their cake, and to eat as well. The MIT and other similar licenses allow this - they get to take the code, extend it, profit off of it, and never give back the changes that made the system better (and arguably forked it).

And if you're lucky, you get mentioned down at the bottom of a copyright/license agreement in 4pt font that's barely readable.

If you 'incorporate' a piece of GPL code into your program, you're either dynamically or statically linking to it - which the FSF considers to be make your work 'derivative' and thus you would be required to license your own work under the GPL, regardless of whether you had made any changes to the original GPL code you make use of or not.

Of course - that's a feature of the GPL - not a bug.

"It only works if everybody does it" is not a feature or a bug, but a recipe for irrelevance at best and coercion at worst.

I think that's why they made the LGPL - though I am unclear on whether that particular version of the license applies to only dynamic linking, or both dynamic and static linking (?).

I'm all for the GPL, but I still don't understand the licensing and how exactly things work through various linking scenarios. It seems to be a question that if asked 5 times you'll get 7 answers.

Since we are talking about licenses, is there a license that is as permissive as MIT but one that requires you to give credit for your work?

Also, is there a license that prohibits giving credit, but is otherwise as permissive?

What do you mean by "give credit"? You have to name the original author with MIT somewhere:

<snip> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </snip>

basically, what I would like is a license that's basically like MIT...but I would want my name + email + tool be listed in the about / licences section of anything created / used with my tools/projects etc.

You may create a A/GPL fork of the project if you wish.

I find the name slightly disrespective of people who develop and work with actual cyclotrons (particle accelerators). How is their application related to cyclotrons?

That name may have a negative ring, as a cyclotron is also a cancer imaging device :


Technically speaking, a cyclotron is just a type of particle accelerator. In medicine I suppose it can imply something more specific (PET imaging but also proton therapy).


Megatron, anyone ?

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact