Future Directions
Category
Published on
Abstract
HUBzero Roadmap and the Future of the CMS
Where we've been, where we are, and where we're going. A brief look at the direction of and changes to HUBzero's Content Management System.
Bio
Michael McLennan is a senior research scientist at Purdue University’s Rosen Center for Advanced Computing, where he is Director of the HUBzero Platform for Scientific Collaboration. He received a Ph.D. in 1990 from Purdue University, supported as an SRC Graduate Fellow, for his dissertation on dissipative quantum mechanical electron transport in semiconductor heterostructure devices. He spent 14 years working in industry at Bell Labs and Cadence Design Systems, developing software for computer-aided design of integrated circuits. He created [incr Tcl], an object-oriented extension of the Tcl scripting language, which has been used by thousands of developers worldwide on projects ranging from the TiVo digital video recorder to the Mars Pathfinder. He coauthored two books, Effective Tcl/Tk Programming (Addison-Wesley, 1997) and Tcl/Tk Tools (O’Reilly Media, 1997). His latest project is the Rappture Toolkit, which accelerates the process of creating scientific tools for simulation and modeling.
Shawn Rice received his M.S. in Information Technology from Purdue University in 2004. With over 15 years of web development experience, his skills and interest run the gamut from server-side programming to client-side scripting to graphic design to accessibility and usability testing. In spring of 2005 he joined the Network for Computational Nanotechnology as a web developer, working primarily on nanoHUB.org, contributing to both the visual design and code. Shawn now also develops code, graphic designs, and offers support for HUBzero projects.
Cite this work
Researchers should cite this work as follows:
Tags
-
1. Future Directions
0
00:00/00:00
-
2. How is HUBzero developed?
46.613279946613282
00:00/00:00
-
3. BOINC: Volunteer Computing
140.54054054054055
00:00/00:00
-
4. How is HUBzero developed?
255.22188855522191
00:00/00:00
-
5. How is HUBzero developed?
353.21988655321991
00:00/00:00
-
6. Make a Wish
534.76810143476814
00:00/00:00
-
7. Future of the CMS
716.4164164164165
00:00/00:00
-
8. In the before times…
738.87220553887221
00:00/00:00
-
9. Portable!
748.64864864864865
00:00/00:00
-
10. Early HUB architecture
755.98932265598933
00:00/00:00
-
11. Stages of the CMS
760.694027360694
00:00/00:00
-
12. It's not me, it's you.
844.310977644311
00:00/00:00
-
13. A typical hub install
862.962962962963
00:00/00:00
-
14. My OCD will not stand for this…
904.50450450450455
00:00/00:00
-
15. Hacks, work-arounds, gum, and …
920.72072072072081
00:00/00:00
-
16. The next HUBzero CMS codename:…
972.3056389723057
00:00/00:00
-
17. Where to start?
1016.4497831164498
00:00/00:00
-
18. Making order from chaos
1023.023023023023
00:00/00:00
-
19. App and Core
1054.5879212545879
00:00/00:00
-
20. Multiple hubs, one core
1133.5335335335335
00:00/00:00
-
21. Bringing it all together
1171.5048381715048
00:00/00:00
-
22. Look Ma, no includes!
1213.1131131131131
00:00/00:00
-
23. Component overrides
1258.0580580580581
00:00/00:00
-
24. What we're working towards
1329.1291291291291
00:00/00:00
-
25. Just a friendly reminder!
1548.4818151484819
00:00/00:00
-
26. Thank you!
1557.9579579579581
00:00/00:00