Created a python file-newfile

.github/workflows/codecov.yml

@@ -15,19 +15,20 @@ jobs:
 
     steps:
       - uses: actions/checkout@main
-      - uses: codecov/codecov-action@v2
+      - uses: codecov/codecov-action@v3
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
 
       - name: Generate coverage report
-        run: |
-          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-          pip install pytest
-          pip install pytest-cov
-          export PYTHONPATH=src
-          pytest --cov=./ --cov-report=xml
+          run:|
+            if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+            pip install pytest
+            pip install pytest-cov
+            export PYTHONPATH=src
+            pytest --cov=./ --cov-report=xml
+
       - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v2
+        uses: codecov/codecov-action@v3
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           directory: ./coverage/reports/

.github/workflows/pylint.yml

@@ -7,7 +7,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.9"]
+        python-version: ["3.11"]
     steps:
     - uses: actions/checkout@v2
     - name: Set up Python ${{ matrix.python-version }}

.github/workflows/python-app.yml

@@ -16,10 +16,10 @@ jobs:
 
     steps:
     - uses: actions/checkout@v2
-    - name: Set up Python 3.9
+    - name: Set up Python 3.11
       uses: actions/setup-python@v2
       with:
-        python-version: 3.9
+        python-version: 3.11
     - name: Install dependencies
       run: |
         python -m pip install --upgrade pip

.gitignore

@@ -143,3 +143,4 @@ schedulebot\ copy.py
 
 # .gitignore 
 config.py
+apifile.txt

Project 2/Readme.md

@@ -0,0 +1,5 @@
+#Youtube video link
+https://youtu.be/crmKjaHUw_E
+
+Group No: 6
+

Project 2/SE Proj2 Rubrics.csv

@@ -0,0 +1,160 @@
+"For each items, score yourself zero (none), one (a litte), two (somewhat), three (a lot).",,,
+,,,
+S.No.,Items,Self-Assessment,Evidence
+,Total points in rubric,90,
+,Total points after assessment,73,
+1,Video,3,The Version 4 submission video was detailed and made it easy for us to follow the steps.
+,,,Version 4 video
+,,,
+,,,
+,,,The 4 min video of new functionality shows a significant delta from prior.
+2,Workload is spread over the whole team (one team member is often X times more productive than the others,2,Contributors
+,,,
+,,,Although this is not an accurate estimate of the workload distribution.
+3,"But nevertheless, here is a track record that everyone is contributing a lot)",2,Contributors
+,,,
+,,,Although this is not an accurate estimate of the workload distribution.
+4,Number of Commits,3,Total Number of Commits - 626
+5,Number of Commits: by different people,2,Apoorva Iyer - 8
+,,,Sai Charitha - 12
+,,,Snigdha Kotharu - 10
+,,,Yashwanth Tanguturi - 6
+,,,
+,,,Command:git shortlog -sn --all
+6,Issues reports: there are many,2,0- total number of issues.
+7,Issues are being closed,2,6 - closed issues
+8,DOI Badge: exists,3,README
+,,,Zenodo
+9,"Docs: doco generated, format not ugly",3,Docs
+10,Docs: what: point descriptions of each class/function (in isolation),3,Functionality
+,,,Function Description
+,,,
+,,,Each class/function is distinctly organized and made easy to understand.
+11,"Docs: how: for common use cases X,Y,Z mini-tutorials showing worked examples on how to do X,Y,Z",3,Mini-tutorials
+,,,
+,,,Each possible use case has been demonstrated and properly documented.
+12,"Docs: why: docs tell a story, motivate the whole thing, deliver a punchline that makes you want to rush and use the thing",3,Version 4 video
+,,,
+,,,"Elaborate documentation,� detailed explanation of the functionality and how to use the bot has made it easy to understand and utilize it to its full capacity."
+13,"Docs: short video, animated, hosted on your repo. That convinces people why they want to work on your code.",2,README
+,,,
+,,,"The documentation, along with a detailed description of the project, has a version 3 submission video and an animated video that made us want to take on this project immediately.�"
+,,,
+,,,"The project is already well executed, but there�s a lot of scope for improvement.�"
+14,Use of version control tools,3,Version Control
+,,,
+,,,Each release has been properly documented.
+15,Use of style checkers,2,Style Checkers
+16,Use of code formatters,2,"There�s no direct evidence on Github. But, they would have most probably used Prettier in VS Code."
+17,Use of syntax checkers,3,Syntax Checkers
+18,Use of code coverage,1,Code Coverage
+19,Other automated analysis tools,1,Workflows
+20,Test cases exist,3,Test Cases
+21,Test cases are routinely executed,1,GitHub Actions
+22,The files CONTRIBUTING.md lists coding standards and lots of tips on how to extend the system without screwing things up,3,Contributiing.md
+23,Issues are discussed before they are closed,2,Discussions
+,,,Few discussions shown on the repository.
+24,Chat channel: exists,3,Discussions Chat seen on the repository.
+25,Test cases: a large proportion of the issues related to handling failing cases.,3,Issues
+,,,There are closed issues whic are handled
+26,Evidence that the whole team is using the same tools: everyone can get to all tools and files,3,Requirements
+27,"Evidence that the whole team is using the same tools (e.g. config files in the repo, updated by lots of different people)",3,Requirements
+28,"Evidence that the whole team is using the same tools (e.g. tutor can ask anyone to share screen, they demonstrate the system running on their computer)",3,Requirements
+,,,
+,,,There is no proof that everyone would be able to run it on their systems.
+29,Evidence that the members of the team are working across multiple places in the code base,2,Commits
+30,Short release cycles,2,Commits
+,,,Release
+,Total items in sustainability evaluation,71,
+,Q1 - What your software does,,
+Q1.1,"Does your website and documentation provide a clear, high-level overview of your software?",Yes,
+Q1.2,Does your website and documentation clearly describe the type of user who should use your software?,Yes,
+Q1.3,Do you publish case studies to show how your software has been used by yourself and others?,Yes,
+,Q2 - Your project's and software's identity,,
+Q2.1,Is the name of your project/software unique?,No,
+Q2.2,Is your project/software name free from trademark violations?,Yes,
+,Q3 - Availability of your software,,
+Q3.1,Is your software available as a package that can be deployed without building it?,No,
+Q3.2,Is your software available for free?,Yes,
+Q3.3,"Is your source code publicly available to download, either as a downloadable bundle or via access to a source code repository?",Yes,
+Q3.4,"Is your software hosted in an established, third-party repository likeGitHub (https://github.com), BitBucket (https://bitbucket.org),LaunchPad (https://launchpad.net) orSourceForge (https://sourceforge.net)?",Yes,
+,Q4 - Your software's documentation,,
+Q4.1,Is your documentation clearly available on your website or within your software?,Yes,
+Q4.2,"Does your documentation include a ""quick start"" guide, that provides a short overview of how to use your software with some basic examples of use?",Yes,
+Q4.3,"If you provide more extensive documentation, does this provide clear, step-by-step instructions on how to deploy and use your software?",Yes,
+Q4.4,"Do you provide a comprehensive guide to all your software�s commands, functions and options?",Yes,
+Q4.5,Do you provide troubleshooting information that describes the symptoms and step-by-step solutions for problems and error messages?,No,
+Q4.6,"If your software can be used as a library, package or service by other software, do you provide comprehensive API documentation?",Not Applicable,
+Q4.7,Do you store your documentation under revision control with your source code?,No,
+Q4.8,"Do you publish your release history e.g. release data, version numbers, key features of each release etc. on your web site or in your documentation?",Yes,
+,Q5 - How you support your software,,
+Q5.1,Does your software describe how a user can get help with using your software?,Yes,
+Q5.2,"Does your website and documentation describe what support, if any, you provide to users and developers?",Yes,
+Q5.3,Does your project have an e-mail address or forum that is solely for supporting users?,No,
+Q5.4,Are e-mails to your support e-mail address received by more than one person?,Not Applicable,
+Q5.5,Does your project have a ticketing system to manage bug reports and feature requests?,No,
+Q5.6,"Is your project's ticketing system publicly visible to your users, so they can view bug reports and feature requests?",Not Applicable,
+,Q6 - Your software's maintainability,,
+Q6.1,Is your software�s architecture and design modular?,Yes,
+Q6.2,Does your software use an accepted coding standard or convention?,Yes,
+,Q7 - Open standards and your software,,
+Q7.1,Does your software allow data to be imported and exported using open data formats?,Yes,
+,"e.g. GIF, SVG, HTML, XML, tar, zip, CSV, JSON, NetCDF, or domain specific ones",,
+Q7.2,Does your software allow communications using open communications protocols?,Yes,
+,"e.g. HTTP, FTP, XMPP, SOAP over HTTP,� or domain-specific ones",,
+,Q8 - Your software's portability,,
+Q8.1,Is your software cross-platform compatible?,Yes,
+,"e.g. does it run under two or more of Windows, Unix/Linux and Mac OS X, or can be used from within two or more of Internet Explorer, Chrome, Firefox and Safari?",,
+,Q9 - Your software and accessibility,,
+Q9.1,Does your software adhere to appropriate accessibility conventions or standards?,No,
+Q9.2,Does your documentation adhere to appropriate accessibility conventions or standards?,No,
+,Q10 - How you manage your source code,,
+Q10.1,Is your source code stored in a repository under revision control?,Yes,
+Q10.2,Is each source code release a snapshot of the repository?,Yes,
+Q10.3,Are releases tagged in the repository?,Yes,
+Q10.4,"Is there a branch of the repository that is always stable? (i.e. tests always pass, code always builds successfully)",Yes,
+Q10.5,Do you back-up your repository?,No,
+��,Q11 - Building and installing your software,,
+Q11.1,Do you provide publicly-available instructions for building your software from the source code?,Yes,
+Q11.2,"Can you build, or package, your software using an automated tool?*",No,
+,"e.g. Make (https://www.gnu.org/software/make/), ANT (http://ant.apache.org/), Maven (https://maven.apache.org/), CMake (https://cmake.org/), Python setuptools (https://pypi.python.org/pypi/setuptools), or R package tools (https://cran.r-project.org/doc/manuals/r-devel/R-exts.html)",,
+11.3,Do you provide publicly-available instructions for deploying your software?,No,
+11.4,Does your documentation list all third-party dependencies?,Yes,
+11.5,Does your documentation list the version number for all third-party dependencies?,Yes,
+11.6�,"Does your software list the web address, and licences for all third-party dependencies and say whether the dependencies are mandatory or or optional?",No,
+11.7�,Can you download dependencies using a dependency management tool or package manager?*,Yes,
+,"e.g. Ivy (http://ant.apache.org/ivy/), Maven (https://maven.apache.org/), Python pip (https://pypi.python.org/pypi/pip) or setuptools (https://pypi.python.org/pypi/setuptools), PHP Composer (https://getcomposer.org/), Ruby gems (https://rubygems.org), or R PackRat (https://rstudio.github.io/packrat/)",,
+11.8�,Do you have tests that can be run after your software has been built or deployed to show whether the build or deployment has been successful?,Yes,
+,Q12 - How you test your software,,
+12.1,Do you have an automated test suite for your software?,Yes,
+12.2,Do you have a framework to periodically (e.g. nightly) run your tests on the latest version of the source code?,No,
+12.3,"Do you use continuous integration, automatically running tests whenever changes are made to your source code?",Yes,
+12.4,Are your test results publicly visible?,Yes,
+12.5,Are all manually-run tests documented?,Yes,
+,Q13 - How you engage with your community,,
+13.1�,"Does your project have resources (e.g. blog, Twitter, RSS feed, Facebook page, wiki, mailing list) that are regularly updated with information about your software?",No,
+,"e.g. release announcements, publications, workshops, conference presentations",,
+13.2,�Does your website state how many projects and users are associated with your project?,No,
+13.3�,Do you provide success stories on your website?,No,
+13.4)�,Do you list your important partners and collaborators on your website?,Not Applicable,
+13.5�,Do you list your project's publications on your website or link to a resource where these are available?,No,
+13.6,Do you list third-party publications that refer to your software on your website or link to a resource where these are available?,No,
+13.7,Can users subscribe to notifications to changes to your source code repository?,Yes,
+13.8�,"If your software is developed as an open source project (and, not just a project developing open source software), do you have a governance model?",No,
+,Q14 - How you manage contributions,,
+14.1,"Do you accept contributions (e.g. bug fixes, enhancements, documentation updates, tutorials) from people who are not part of your project?",Yes,
+14.2,Do you have a contributions policy?,Yes,
+14.3,Is your contributions' policy publicly available?,Yes,
+14.4�,Do contributors keep the copyright/IP of their contributions?,Yes,
+,Q15 - Your software's copyright and licensing,,
+15.1�,Does your website and documentation clearly state the copyright owners of your software and documentation?,Yes,
+15.2,�Does each of your source code files include a copyright statement?,No,
+15.3,Does your website and documentation clearly state the license of your software?,Yes,
+15.4,Is your software released under an open source license?,Yes,
+15.5�,Is your software released under an OSI-approved open-source license?,Yes,
+15.6,Does each of your source code files include a license header?,No,
+15.7�,Do you have a recommended citation for your software?,Yes,
+,Q16 - Your plans for the future,,
+16.1,"Does your website or documentation include a project roadmap (a list of project and development milestones for the next 3, 6 and 12 months)?",Yes,
+16.2,"Does your website or documentation describe how your project is funded, and the period over which funding is guaranteed?",No,
+16.3�,"Do you make timely announcements of the deprecation of components, APIs, etc.?",No,